​
Connect Tacit to Claude.ai

Tacit exposes its full scenario authoring surface, agent catalogue, and evaluation data through a remote Model Context Protocol (MCP) server. Once connected, Claude can list, create, and refine scenarios, identities, personalities, rubrics, and everything else in your org, all through natural-language tool calls.
The connector uses OAuth 2.1 with Dynamic Client Registration. You don’t need to copy API keys or paste client secrets. Just paste one URL.

​
Prerequisites

  • A Tacit account that is a member of at least one organization
  • Claude.ai (web, Desktop) with custom connector support, or Claude Code CLI

​
Setup

​
Step 1: Copy the connector URL

https://api.tacitintelligence.co/mcp

​
Step 2: Add it to Claude

  1. Open Claude.ai and go to Settings → Connectors
  2. Click Add custom connector
  3. Name it Tacit (or anything you like)
  4. Paste https://api.tacitintelligence.co/mcp as the URL
  5. Leave the Advanced settings → OAuth Client ID / Secret fields blank
  6. Click Add

​
Step 3: Sign in and allow access

Claude redirects your browser to a consent screen that says:
Sign in to Claude with Tacit Intelligence Co. Claude is requesting to:
  • Verify your identity
  • View your personal profile information
  • Maintain access to your data even when you’re not actively using the app
Click Allow. You are returned to Claude and the connector shows as Connected. That’s it. Ask Claude something like “List my Tacit scenarios” to confirm the connection works.

​
Which organization gets connected?

The connector is bound to the Tacit organization you were the active member of at the moment you clicked Allow. Claude sees data from that organization only; it cannot read or write data from other organizations you belong to.

​
To change organizations

If you belong to multiple Tacit organizations and want to point Claude at a different one:
  1. In Claude settings, remove the existing Tacit connector
  2. Open https://platform.tacitintelligence.co and switch to the desired organization
  3. Re-add the connector from Step 2 above
The new consent screen will be bound to the organization you’re now active in.
This friction is a security feature, not a limitation. Each organization requires its own explicit consent so you never accidentally expose data from one organization while working with another.

​
What Claude can do

Once connected, Claude has access to the full Tacit MCP tool surface: scenarios, identities, personalities, artifacts, decisions, rubrics, best practices, scope boundaries, terminology, and more. Try prompts like:
  • “Create a scenario about a nurse triaging a patient with chest pain”
  • “Show me all the rubrics linked to scenarios in this org”
  • “Search for identities that match ‘community pharmacist’”
  • “Add a hidden-state item to scenario X that says the patient has an undiagnosed heart murmur”

​
Troubleshooting

​
”Couldn’t reach the MCP server”

Rare. This usually means Anthropic’s backend couldn’t register Claude as an OAuth client with our identity provider (Stytch). If you see this, try again in a few minutes. If it persists, include the ofid_... reference from the error message when contacting support.

​
”Authorization with the MCP server failed”

This means the OAuth exchange completed but the token isn’t valid for any Tacit organization. The most common cause is trying to reconnect while logged in as a different user. Sign out of platform.tacitintelligence.co, sign back in as the expected user, then re-add the connector.

​
Tools don’t appear after connecting

Try sending any message in Claude; tools are loaded lazily. If tools still don’t appear, disconnect and reconnect. Claude re-fetches the tool list during connection.

​
Revoking access

  1. From Claude: Settings → Connectors → Tacit → Remove
  2. From Tacit: Ask your org admin to revoke the Connected App in the Tacit admin dashboard (invalidates all active tokens for that client)

​
Security and privacy

  • The connector authenticates using short-lived OAuth 2.1 access tokens signed by our identity provider, Stytch. Tokens are refreshed automatically and expire quickly if Claude stops using them.
  • Dynamic Client Registration means Claude registers itself as a client each time; no long-lived secret ever lives in Claude or in your Claude settings.
  • Every tool call is audited server-side with org, member subject, tool name, and timestamp.
  • Tacit’s MCP server respects the same row-level security policies as the web app. Claude sees exactly the data your authenticated user would see in Tacit, nothing more.

​
Support

Questions or issues? Email support@tacitintelligence.co.