Profound can be connected to Agen.co two ways, matching the Official / In-house filter in the connector picker:
- Official — Agen.co connects through Profound's own hosted MCP server, so your AI agents use the same visibility, sentiment, citation, and traffic reports available in the Profound product itself, scoped to each signed-in user's own Profound access.
- In-house — Agen.co wraps Profound's REST API directly through its own integration layer, authenticating with an organization-level API key.
Pick Official first — it requires no API key management and keeps every query scoped to the signed-in user. Fall back to In-house if you need an organization-wide API key instead of per-user sign-in.
Prerequisites
Prerequisites
- A Profound account, with the categories, domains, and prompts you want tracked already configured in Profound
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- In the search bar, type
Profoundand select it from the results. - Optionally fill in Instance Slug — distinguishes multiple instances of this MCP connector by prefixing each imported tool as
slug__tool. Use lowercase kebab-case; leave empty for a single instance. This value is immutable after creation. - Click Connect.
You're redirected to Profound to sign in and approve access. No Client ID, Client Secret, or backend URL is needed — Profound's MCP server is a single hosted endpoint that Agen.co already knows how to reach.
Profound's standard authentication is per user — every tool call runs as the person who signed in, and only returns data that person can access in Profound. If several people on your team want their AI agents to query Profound, each of them completes this sign-in individually, rather than one admin authorizing access for the whole org.
Once connected, Profound appears under My connectors with the following tools available to enable:
| Group | Tools | What they do |
|---|---|---|
| Discovery | whoami, list_organizations, list_regions, list_models, list_categories, list_domains, list_tags, list_topics, list_prompts | Resolve human-readable context (organizations, tracked AI models, categories, domains, prompts) into the IDs the report tools need |
| Brand visibility & sentiment | get_visibility_report, get_sentiment_report, get_citations_report, get_prompt_answers | Measure how prominently and how positively your brand appears in AI-generated answers, which domains AI engines cite, and the raw underlying answers |
| Traffic & bot analysis | get_referrals_report, get_bots_report | Track visits AI engines refer to your domain and monitor AI crawler activity (for example GPTBot, PerplexityBot) hitting your site |
Profound also supports a long-lived bearer token (API key) as an alternative to per-user OAuth, intended for service accounts and automation rather than individual sign-in. This requires a Profound Enterprise plan and approval from Profound's support team, and the key is generated from the API Keys page in Profound's account settings. This mode is account-level rather than per-user. Agen.co's Official connector form doesn't currently expose a separate bearer-token field — the steps above cover the standard OAuth path.
Enabling the Profound connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.