Profound

Query Profound AI-search visibility, citation and bot-traffic analytics, and build or run Profound Agents.

Add to Agentman Studio

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

Resources

What the Profound connector does

The Profound MCP server connects a Profound workspace — an AI-search analytics platform measuring how brands appear in AI-generated answers — to Claude, ChatGPT and any MCP-compatible agent. It answers questions about brand visibility, citations, sentiment and AI crawler traffic, and it can build, publish and run Profound Agents. Sign-in is OAuth, or an Enterprise API key.

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.

Profound tools (2)

  • search_docs
  • execute

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The tool count in the directory tells you nothing about the surface. Two names, thirty documented capabilities, zero overlap. Do not size the connector's reach from the listing, and do not read search_docs and execute as a boundary.
  • No application scopes exist. The server's RFC 9728 descriptor at /.well-known/oauth-protected-resource/mcp declared scopes_supported as an empty list on 2026-08-22, and the authorization server advertises only email, offline_access, openid and profile. No boundary falls between reading a report and publishing an Agent, because there is no boundary at all. Profound's role-based access control is the real limit, and it applies to the user, not to the connection.
  • Profound's two oauth-protected-resource documents disagree with each other. The one at the /mcp path declares scopes_supported: []; the one at the bare .well-known path omits the field entirely and adds a resource_name. Both were served on 2026-08-22. The /mcp one is the document the www-authenticate header points at, so it is the operative one.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request. Every parameter detail on this page comes from Profound's documentation, not from a handshake.
  • Profound's capability pages lag its changelog. The changelog describes Docs create/read/ search/revise/rename/share, Knowledge Base document upload, Projects list/accept/work, Shopping and FactCheck all arriving through the MCP, none of which appears on the two capability pages. The documented 30 is therefore also a floor.
  • run_agent has no preview default. The build and publish tools default to preview: true; starting a run does not. If your Agent contains a WordPress publish step or a Gmail node, the MCP client has no way to see that before the run begins.
  • The API-key route is Enterprise-only and requires support to grant API access separately.
  • The server card's documentationUrl is wrong. It points at docs.tryprofound.com/agent-apis/mcp/overview, which redirects to /mcp/overview. Harmless, but it means the card and the docs tree were versioned apart.

Frequently asked questions

How many tools does the Profound MCP server have?

Two by Anthropic's count and thirty by Profound's own documentation, and the two lists share no names. Anthropic's directory lists search_docs and execute. Profound's capability pages describe seventeen analytics tools and thirteen Agent tools, none of which is called search_docs or execute. Read the directory's two as an entry point rather than as the surface.

What can the Profound connector actually reach?

Your organization's AI-search analytics, your tracked prompts, and your Profound Agents. That covers visibility, citation, sentiment, FactCheck, Shopping, AI bot traffic and referral reports, plus the ability to build, publish and run Agents. Profound's changelog also lists Docs, Knowledge Base and Projects reaching the connector after its capability pages were written.

Is the Profound MCP server read-only?

No, and Profound's own two descriptions disagree. Its analytics capability page states all tools are read-only. The server's machine-readable card at mcp.tryprofound.com summarises its writes as prompt creation, updates, status changes and agent execution. The card describes the whole server; the capability page describes only the analytics half of it.

What OAuth permissions does the Profound MCP server request?

None that narrow anything. The server's RFC 9728 descriptor declared an empty scopes_supported list on 2026-08-22, and its authorization server advertises only email, offline_access, openid and profile. Those are identity claims, not application permissions, so consent cannot separate reading a report from publishing an Agent.

Can the Profound connector publish content to my website?

Indirectly, if you built an Agent that does. Profound's changelog states the MCP supports Agents built with third-party nodes including WordPress, Search Console, Google Docs, Gmail and ChatGPT Ads. Its WordPress documentation describes a Create Post step taking a Status of Draft or Publish, so running such an Agent can publish live.

Do I need a paid Profound plan to use the MCP server?

You need a Profound account, and an Enterprise plan for the API-key route. Profound documents OAuth as the recommended method for all connections and the long-lived Bearer token as requiring an Enterprise plan plus support-granted API access. Its REST API documentation states the API is available to Enterprise customers only.

Does the Profound connector work with ChatGPT?

Yes, through ChatGPT developer mode. Profound documents enabling Developer mode under Security and login, creating a plugin on the ChatGPT Plugins page with the server URL and OAuth authentication, then installing it. The setup requires a ChatGPT account on a plan that supports developer mode and a Profound account.

Why do Profound tools not appear after I add the server?

Usually the client has not reloaded its MCP configuration. Profound's own troubleshooting says to restart the client, because some clients read MCP config only at startup. If authentication itself fails, Profound advises disconnecting the existing connection and reconnecting, or clearing cached OAuth tokens in the client.

Sources

More Sales & CRM connectors

  • Abency

    Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.

  • Actively

    Read per-account sales intelligence — agent memory, decisions, signals — from an AI agent.

  • Adobe Journey Optimizer

    Inspect campaigns, journeys and channel configurations in Adobe Journey Optimizer from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Profound to work.

Connect Profound once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio