Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Query Third Bridge's 100,000+ expert interview transcripts.
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 Third Bridge MCP server connects an expert-network research subscription to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists one read-only tool that queries Third Bridge's library of more than 100,000 expert interview transcripts in natural language. Sign-in is OAuth, and a separate pilot agreement governs the connector.
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.
openid, profile, email and offline_access. Three are identity claims and the fourth is a refresh token. Nothing at the OAuth grant separates one kind of content from another, and no boundary falls anywhere except at your subscription entitlements.readOnlyHint, destructiveHint or parameter detail is published here. The read-only characterisation is Anthropic's directory record plus the vendor's own description, not the server's declaration to us.third-bridge-debug-prompt. Their content is unknown to us.One. Anthropic's directory lists a single tool, third_bridge_content_query, and Third Bridge publishes no tool list of its own to check that against. The whole connector is one natural-language query against the transcript library, so what it can reach is decided by that query and by your subscription entitlements, not by a menu of tool names.
No. Anthropic's directory records the connector's permissions as Read only, the single tool is a content query, and the OAuth grant type list includes nothing that implies a write. Third Bridge's own MCP page describes retrieval and synthesis exclusively. Nothing we found in the vendor's material describes the connector modifying Third Bridge data or your workspace.
Four, and none of them narrows anything. The server's RFC 9728 descriptor and its authorization server metadata both advertised openid, profile, email and offline_access on 2026-08-22. Three are OpenID identity claims and the fourth grants a refresh token. No scope names transcripts, the library, or any data boundary at all.
Yes, and they are easy to miss. Third Bridge publishes Pilot MCP Terms at a URL present in its sitemap but absent from its own compliance policies index. Those terms supplement your existing Content agreement, grant access on a two-week pilot basis only, and require that your LLM subscription prohibits training on inputs and outputs.
Third Bridge's Pilot MCP Terms say no, in effect. They require you to confirm that your company's agreement with your LLM provider is a commercial or enterprise subscription which prohibits the use of inputs and outputs for model training. A personal or consumer tier that does not carry that prohibition would not satisfy the condition you are asked to confirm.
No. Third Bridge's Pilot MCP Terms state plainly that you will not use MCP to bulk extract Third Bridge Content. The underlying Content Terms and Conditions are stricter still, forbidding clients from copying, reproducing, forwarding or distributing Content, and licensing it for internal research purposes only.
Transcripts of vetted expert interviews, and no. Third Bridge's Content Terms and Conditions reserve all intellectual property in transcripts, forbid reproducing or republishing them, and require clients to keep Content strictly confidential within their own organisation. An agent that pastes a transcript passage into an external deliverable would breach that clause.
Third Bridge says it does, and the mechanism is citation rather than a guarantee. Its MCP page describes surfacing citation-backed insights instantly to reduce hallucination risk. But its Content Terms disclaim all warranty as to accuracy or completeness, and the Pilot MCP Terms disclaim any warranty over LLM responses containing that content.
llms.txt (retrieved 2026-08-22). robots.txt is Allow: / with no Content-Signal line. · retrieved 2026-08-22https://ai.thirdbridge.com/mcp/sse returned HTTP 401 with a WWW-Authenticate: Bearer challenge naming the resource metadata document; RFC 9728 descriptor at https://ai.thirdbridge.com/.well-known/oauth-protected-resource and authorization server metadata at https://ai.thirdbridge.com/.well-known/oauth-authorization-server both retrieved (2026-08-22) · retrieved 2026-08-22https://ai.thirdbridge.com/ — served application bundle inspected for result structure (retrieved 2026-08-22) · retrieved 2026-08-22Connect Third Bridge once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.