Profound
by Profound
Query Profound AI-search visibility, citation and bot-traffic analytics from an AI agent, and build or run Profound Agents. Anthropic lists 2 tools; Profound's own documentation describes 30. OAuth or an enterprise API key, no application scopes.
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.
Connect Profound via MCP
https://mcp.tryprofound.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Profound Tools & Capabilities (2)
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_docsandexecuteas a boundary. - No application scopes exist. The server's RFC 9728 descriptor at
/.well-known/oauth-protected-resource/mcpdeclaredscopes_supportedas an empty list on 2026-08-22, and the authorization server advertises onlyemail,offline_access,openidandprofile. 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-resourcedocuments disagree with each other. The one at the/mcppath declaresscopes_supported: []; the one at the bare.well-knownpath omits the field entirely and adds aresource_name. Both were served on 2026-08-22. The/mcpone is the document thewww-authenticateheader 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_agenthas no preview default. The build and publish tools default topreview: 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
documentationUrlis wrong. It points atdocs.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
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.
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.
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.
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.
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.
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.
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.
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
- Profound MCP overview (retrieved 2026-08-22).
www.tryprofound.com/docs/mcp, the URL in Anthropic's directory, redirects todocs.tryprofound.com/introductionrather than to this page. · retrieved 2026-08-22 - Profound MCP analytics capabilities (retrieved 2026-08-22) · retrieved 2026-08-22
- Profound MCP Agents capabilities (retrieved 2026-08-22) · retrieved 2026-08-22
- Profound MCP authentication (retrieved 2026-08-22) · retrieved 2026-08-22
- Profound MCP connection guides — · · (retrieved 2026-08-22) · retrieved 2026-08-22
- Profound documentation index,
llms.txt(retrieved 2026-08-22) · retrieved 2026-08-22 - Profound REST API authentication and changelog — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Profound roles and permissions (retrieved 2026-08-22) · retrieved 2026-08-22
- Profound WordPress Agent steps (retrieved 2026-08-22) · retrieved 2026-08-22
- Profound OpenAPI specification, 111 paths and 121 operations (retrieved 2026-08-22) · retrieved 2026-08-22
- Profound product changelog, entries dated 2026-07-24, 2026-07-31 and 2026-08-07 (retrieved 2026-08-22) · retrieved 2026-07-24
- Profound MCP server card (retrieved 2026-08-22) · retrieved 2026-08-22
- Live OAuth posture check: anonymous
initializereturned HTTP 401 with awww-authenticateBearer challenge; RFC 9728 metadata athttps://mcp.tryprofound.com/.well-known/oauth-protected-resource/mcp; authorization server metadata athttps://auth.tryprofound.com/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 docs.tryprofound.com/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— synthesis of this documentation into our prose is expressly permitted by the publisher (retrieved 2026-08-22) · retrieved 2026-08-22- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Profound support — <mailto:support@tryprofound.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Sales & CRM
- Developer
- Profound
- Tools
- 2
- Domain
- mcp.tryprofound.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.