IntegrationModel Context ProtocolOAuth 2.1

CitePatch MCP Server

Connect Cursor, Claude, Codex, VS Code, ChatGPT, and any MCP-compatible agent to your CitePatch workspace — projects, visibility metrics, opportunities, Brand Truth, and patches. One secure endpoint. One-click OAuth. No API keys to copy.

Endpointhttps://mcp.citepatch.com/mcp

Model Context Protocol

What is the CitePatch MCP server?

The Model Context Protocol (MCP) is an open standard that lets AI assistants talk to tools and data through one consistent interface. CitePatch exposes your AI Search Patch Loop as an MCP server, so your agent can read evidence, draft patches, and submit them — without copy-paste.

It runs on Streamable HTTP at a single endpoint and authenticates with OAuth 2.1 — your client opens CitePatch consent, you pick the organization, and you approve exactly which scopes to grant. No API keys to create or paste. Write actions are confirmation-gated.

  • Works with any MCP client — Cursor, Claude Code, VS Code, ChatGPT, Codex.
  • One-click OAuth — approve read, write, or apply on a consent screen.
  • 14 tools on the full surface; 12 on /mcp/readonly (submit/apply omitted).
  • Evidence labeled honestly; external model text fenced as untrusted.

What your agent can do

You approve scopes at sign-in. Grant only what you need — anything outside them is rejected.

Read & diagnose

read scopes

See your workspace the way CitePatch sees it — without leaving the agent.

  • List projects and pull a project briefing
  • Check AI visibility metrics and tracked prompts
  • Inspect opportunities, evidence chains, and Brand Truth
  • Review patches and experiment results

Submit patches

patches:write

Draft content changes in the agent, then send them into CitePatch.

  • Get an authorship brief for an opportunity
  • Submit a patch with confirmation before it lands
  • Keep BeforeSHA checks against your live connector

Apply patches

patches:apply

When the org allows it, open a reviewable PR or draft from the agent.

  • Apply an approved patch via your connector
  • Confirmation-gated — nothing ships on the first call
  • Requires org mcp_apply_enabled plus the apply scope

Built-in prompts (brief-me, close-gap) walk the agent through briefing and closing a gap step by step.

Connect in 3 steps

  1. Add the connector

    Point your MCP client at https://mcp.citepatch.com/mcp — a CLI command in Claude Code, a JSON line in Cursor, or an HTTP entry in Codex. Configs below.

  2. Sign in and approve

    Your client opens CitePatch OAuth in the browser. Sign in, choose the organization, review scopes (read, write, apply), and Approve.

  3. Start working

    The client stores a short-lived token with the org bound in. Ask your agent about visibility gaps, evidence, or patch drafts — no headers to configure.

Wire it into your agent

Point any MCP client at https://mcp.citepatch.com/mcp (Streamable HTTP). The first call triggers CitePatch OAuth — pick an org, grant scopes, done. No API keys, no custom headers. For inspection only, use https://mcp.citepatch.com/mcp/readonly.

Drop citepatch into your global MCP list, or commit a project file so the whole team gets the same connector.

  1. In Cursor, open Settings → MCP and choose Add new global MCP server — or edit ~/.cursor/mcp.json directly.
  2. Insert the JSON below, save, then reload MCP (restart Cursor if citepatch stays offline).
  3. Authenticate when Cursor prompts you — Login beside citepatch, or the first tool call.
  4. Optional: commit .cursor/mcp.json in the repo so teammates inherit the same endpoint.
.cursor/mcp.json
{
  "mcpServers": {
    "citepatch": {
      "url": "https://mcp.citepatch.com/mcp"
    }
  }
}

Try it

Once connected, talk to your agent in natural language. It picks the right tools.

Brief

“Use citepatch_get_workspace then brief me on our top visibility gaps for the main project.”

Diagnose

“List opportunities and show evidence for the highest-impact owned gap.”

Author

“Get the patch brief for opportunity X and draft a minimal content change grounded in Brand Truth.”

Verify

“Show experiment ledger entries and whether any patch correlated with a visibility change — do not claim causality.”

Built-in guardrails

Protections

  • OAuth 2.1 with PKCE — short-lived tokens, revocable instantly in Settings → MCP.
  • Org isolation — organization is signed into the token; tenant args are rejected.
  • Write tools require confirmation handles; apply also needs org mcp_apply_enabled.
  • Honesty contract — evidence labels, metric cells, untrusted fences on external text.

Privacy & data

MCP calls send your AI client exactly what each tool returns — no raw embeddings dump, no internal metadata. Write tools need their own scope and leave an audit trail. We do not use your workspace data to train third-party models.

Connect CitePatch to your AI agent

Add the endpoint, approve access in one click, and let your agent work the Patch Loop with real evidence.