Apparently MCP · Connector setup

Put regulatory steering inside the agent writing your product.

Name: Apparently
Availability: PreOrder

Connect the live Apparently MCP endpoint to Claude Code, Claude, ChatGPT, or any compatible agent. The connection status below distinguishes what works now from what still requires Apparently OAuth.

Remote MCP endpointhttps://www.apparently.cc/mcp

Not checked yet · run a live tools/list request without sending a credential.

Terminal + IDE

Connect Apparently to Claude Code

Available now

Activation path

Add the remote server with a bearer key.

Download setup

Create an Apparently API key
Sign in, create a key, and save it once in your local secrets manager.
Run the setup command
Copy the command shown here, or download the equivalent JSON when the workspace manages MCP configuration as code.
Set APPARENTLY_API_KEY
Expose the key only to Claude Code. Do not commit it or place it in a repository-level configuration file.
Restart and verify
Restart Claude Code, confirm the four Apparently tools appear, then run the test prompt below.

Create API key Official setup docs

Connection readinessWhat is live today

Remote MCP endpoint: Live
Bearer API keys: Live
Apparently OAuth: Status unavailable

Claude Code and custom clients that accept request headers work now. Hosted provider readiness is read from this deployment; plan and administrator controls still determine whether each user can add the connector.

ConfigurationClaude Code command

claude mcp add --transport http --scope user apparently https://www.apparently.cc/mcp \
  --header "Authorization: Bearer ${APPARENTLY_API_KEY}"

Tools returned by the live endpointFour governed actions

evaluate_actionReview a code change, command, or deployment before execution.
evaluate_changesetReview a whole diff or commit at once, rather than file by file.
legal_advisoryAnalyze a regulatory or legal question with controls and confidence.
escalate_to_legalRoute a material judgment to the appropriate human legal queue.
escalation_statusRetrieve the current status and resolution of an escalation.

Connection testTry this after activation

Before changing payments/loyalty.ts to redeem purchased points for cash, evaluate the change across every planned launch jurisdiction. Return the legal issue, authority, safer code paths, required licences, approvals, and citations. Do not execute or merge until the route is authorized.

The agent should call evaluate_action before proposing a release.

Apparently coding workspacePrefer a governed coding agent with Apparently already in the loop?Sign In to Code