Citera home
Browse documentation

Connect Citera to Claude

Connect Citera to Claude

Connect Claude and Claude Code to Citera with browser sign-in, then verify read-only brand access.

Summarize with AIChatGPTClaudePerplexity

Before you connect

Sign in to Citera and open Settings → API & MCP → MCP. Select Connect another assistant. Choose your client, or Other client when it is not listed, and copy the server URL. API and MCP access are open to all Citera accounts.

Open Citera API & MCP settings

The current server URL is https://mcp.citeralabs.ai/mcp. Browser sign-in lets you select the brands your assistant may read without creating an API key. The connection is read-only; it does not grant content generation or publishing access.

Connect Claude

  1. In Claude, open Connectors in Settings or Customize and add a custom connector named Citera.

  2. Enter https://mcp.citeralabs.ai/mcp as the remote server URL.

  3. Choose Sign in now and Use Claude’s published identity when those options appear. Leave request headers empty for browser sign-in.

  4. Finish adding the connector, sign in to Citera, select the brands it may read and review the consent screen.

  5. Enable Citera in the conversation’s connectors menu. Organization owners may need to add or allow the custom connector first.

Connect Claude Code

If Citera already appears in Claude Code’s /mcp menu through your Claude account, use that connection. Otherwise, add the remote server with this command, then open /mcp, select Citera and complete browser sign-in.

claude mcp add --transport http --scope user citera 'https://mcp.citeralabs.ai/mcp'
claude mcp add --transport http --scope user citera 'https://mcp.citeralabs.ai/mcp'
claude mcp add --transport http --scope user citera 'https://mcp.citeralabs.ai/mcp'
claude mcp add --transport http --scope user citera 'https://mcp.citeralabs.ai/mcp'

Claude Code MCP reference

Verify the connection

Enable Citera in your client and send this first request. Inspect the Citera tool result: it should list only brands you authorized. A written answer without a Citera tool call does not verify a connection.

Use the Citera MCP tools to list the brands I authorized. Show their names and IDs. Then ask which brand I want to review. Do not change, generate or publish anything.

Permissions, limits and troubleshooting

Claude’s custom-connector availability and organization roles apply. Citera’s browser sign-in is read-only even when the client can run write tools from other servers. Use the shared client setup guide for the optional manual-key route.

A brand with no completed scans may have little visibility data to report. If a brand is missing, check the account used for sign-in and the brands selected during consent. Reconnect when needed. You can revoke the connection under AI assistants in Citera’s MCP settings. API and MCP share the account’s applicable usage allowance.

Client menus, plan requirements and connection capabilities can evolve. These instructions describe configuration and a verification step; they do not guarantee that every client version or workspace policy allows the connection.

Try a complete workflow

Weekly AI visibility brief

White label client report

Find pages losing visibility

Client reference

Official Claude documentation