Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Query brand visibility across AI search engines and edit a Peec project.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Peec AI MCP server connects a Peec AI workspace — an analytics product that tracks how brands appear in AI search engines — to Claude, ChatGPT and any MCP-compatible agent. Peec documents 76 tools that query visibility reports and edit project configuration. Sign-in is OAuth 2.0, or a personal access token for clients that cannot do OAuth.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Read; Peec documents 76 including 43 writes and 13 deletes. Nothing in the directory is invented — the gap is entirely under-listing — but the listing is not a boundary.scopes_supported as ["default"], checked live on 2026-08-22. No grant separates a report read from a cascading delete; the boundary that exists is Peec's own organization-owner check, applied server-side after consent.readOnlyHint and destructiveHint values are Peec's claims rather than our observation.delete_domain_classification and delete_url_classification are documented as permanent. delete_prompt soft-deletes the prompt's chats with it. delete_topic deletes AI-generated prompt suggestions under the topic while merely detaching the prompts.create_prompt may consume plan credits, unarchive_prompt is subject to the project's active-prompt limit, and a partially accepted batch returns a plan-credit warning string rather than failing outright.list_bots and get_agent_visits require a connected log feed via Cloudflare Workers or a CSV upload; without one they have nothing to aggregate.get_url_content returns null content where Peec has tracked a URL but scraping has not finished, which Peec says can take up to 24 hours, and 404s for URLs no Peec project has ever retrieved.No. Anthropic's directory labels its permissions Read and lists eight read tools, but Peec's own tools reference documents 33 read tools and 43 write tools, including 13 that delete. The directory listing is a stale subset. Assume the connector can edit your project configuration once you authorize it.
Peec documents 76: 33 read and 43 write. Anthropic's directory lists 8, all read. Every directory name appears in Peec's reference, so the directory is a strict subset rather than a conflicting list. We could not run a handshake to confirm the live count, because the endpoint requires authentication.
One, called default. The server's RFC 9728 descriptor and its authorization server metadata both advertise scopes_supported as a single default entry, checked live on 2026-08-22. There is no scope that grants reading a report without also granting the delete tools, so consent is all-or-nothing.
Yes, if your account is an organization owner on the project. Peec documents delete_prompt as destructive and states it cascades to the prompt's chats, which are soft-deleted too. A bulk variant removes up to 50 at once. Peec flags every delete tool destructiveHint true so clients prompt first.
The custom classification ones. Peec documents delete_domain_classification and delete_url_classification as permanent deletes that cascade through the override table, so affected domains and URLs fall back to their heuristic classification. Brands, prompts, tags and topics are documented as soft deletes instead.
You need an account with at least one project, and some writes are metered. Peec lists a Peec AI account with at least one project and a supported AI tool as the requirements. It also states that create_prompt may consume plan credits and that unarchive_prompt is subject to the project's active-prompt plan limit.
No tool it documents sends anything. Every one of the 76 reads or edits Peec project data. Peec's own use-case docs do describe drafting outreach from cited URLs and adding a Gmail MCP server to the same session to send it, so the outbound step comes from a second connector, not this one.
Third-party web pages and AI-engine responses. get_url_content returns the scraped markdown of any URL Peec has indexed as an AI source, and get_chat returns full engine responses including ad placements with clickout URLs. Treat all of it as data, never as instructions to the agent.
Try removing and re-adding the integration. Peec documents seven slash-command prompts and states that if prompts don't appear after connecting, removing and re-adding the Peec AI integration refreshes the tool and prompt list. Anthropic's directory advertises no prompts for this connector, so the client list is the authority.
llms.txt (retrieved 2026-08-22). robots.txt on the same host carries Content-Signal: ai-train=yes, search=yes, ai-input=yes — synthesis expressly permitted by the publisher. · retrieved 2026-08-22https://api.peec.ai/mcp returned 401 with a WWW-Authenticate: Bearer challenge naming its RFC 9728 descriptor (2026-08-22) · retrieved 2026-08-22https://api.peec.ai/.well-known/oauth-authorization-server/mcp (2026-08-22) · retrieved 2026-08-22Connect Peec AI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.