MCP Guide / Supported Agents
Connect any AI agent to Anchor.
Step-by-step setup for every MCP-compatible agent. One URL, OAuth sign-in, and you're done.
https://mcp.anchor.cc/mcp
Claude Web
- Open Claude Web Connectors settings.
- Click Add custom connector.
- Name it Anchor and paste the server URL:
https://mcp.anchor.cc/mcp - Click Add, then Connect. A Google sign-in window opens — use the account tied to your Anchor workspace.
- In any new conversation, enable the Anchor connector from the tools panel and start prompting.
Try: "Create an Anchor table called Leads with columns for name, email, company, and status, fill in some data, then build a kanban app on top of it."
Claude Desktop
- Open Claude Desktop and go to Customize → Connectors.
- Click the + button, then choose Add custom connector.
- Name it Anchor and paste:
https://mcp.anchor.cc/mcp - Click Connect. A browser window opens for Google sign-in — approve to finish.
- The Anchor connector is now available across all tabs — Chat, Cowork, and Code.
Claude Code
Option A — one-line install
- Run:
claude mcp add --transport http anchor https://mcp.anchor.cc/mcp - Start Claude Code with
claudeand trigger any Anchor tool — your browser opens for Google sign-in on first use. - Verify the connection with
/mcpinside Claude Code. Anchor should appear as connected.
Option B — edit the config file
- Open
~/.claude/mcp.json(create it if missing). - Add Anchor under
mcpServers:
{
"mcpServers": {
"anchor": {
"type": "http",
"url": "https://mcp.anchor.cc/mcp"
}
}
}
- Restart Claude Code. The OAuth flow runs on first tool call.
ChatGPT
- Open chatgpt.com and go to Settings → Connectors.
- Choose Add connector → Custom MCP.
- Fill in:
- Name: Anchor
- URL:
https://mcp.anchor.cc/mcp - Authentication: OAuth (auto-discovered)
- Click Save, then Connect and complete the Google sign-in.
- In a chat, open the Tools menu, enable Anchor, and describe what you want built.
Codex
- Open (or create)
~/.codex/config.toml. - Add an entry for Anchor:
[mcp_servers.anchor]
type = "http"
url = "https://mcp.anchor.cc/mcp"
- Run any Codex command. The first Anchor tool call triggers a browser OAuth flow — sign in with Google.
- Confirm the connection with
codex mcp list.
Gemini Enterprise
- Sign in to the Gemini Enterprise admin console.
- Go to Agents → Tools → MCP servers and choose Add server.
- Fill in:
- Name: Anchor
- Transport: HTTP
- URL:
https://mcp.anchor.cc/mcp - Auth: OAuth 2.0 (auto-discovered)
- Save. Attach Anchor to any agent template you want it available in — each end user authenticates with their own Google account the first time they call an Anchor tool.
Tip: Because each user signs in individually, Anchor permissions map cleanly to your existing team structure — no service accounts required.
Gemini CLI
- Open
~/.gemini/settings.json(create it if missing). - Add Anchor under
mcpServers:
{
"mcpServers": {
"anchor": {
"httpUrl": "https://mcp.anchor.cc/mcp"
}
}
}
- Launch Gemini CLI with
gemini. - Type
/mcpto list connected servers. Anchor should appear; the first tool call triggers a browser OAuth flow.
Grok
- Open grok.com and go to Settings → Tools & connectors.
- Choose Add MCP server.
- Fill in:
- Name: Anchor
- URL:
https://mcp.anchor.cc/mcp
- Save and complete the Google sign-in when prompted.
- Enable the Anchor tool from the chat toolbar before prompting.
Microsoft Copilot
- Open Copilot Studio and pick (or create) the agent you want to extend.
- Go to Tools → Add a tool → Model Context Protocol.
- Register a new MCP server:
- Name: Anchor
- URL:
https://mcp.anchor.cc/mcp - Authentication: OAuth 2.0 (dynamic registration)
- Publish the agent. Users in your tenant sign in with their Google-linked Anchor account the first time they call a tool.
Note: MCP support is currently in public preview across the Copilot family. The connector path may differ slightly in Copilot for Sales, Service, and Finance SKUs.
Any other MCP-compatible agent
Anchor follows the Model Context Protocol spec exactly. If your agent supports remote MCP servers with OAuth 2.0, it can use Anchor today — no extra work required.
- Transport: Streamable HTTP
- URL:
https://mcp.anchor.cc/mcp - Auth: OAuth 2.0 with PKCE, dynamic client registration enabled
- Scopes: none required — access is scoped to the signed-in user's Anchor permissions
Don't see your agent listed? Tell us and we'll add a walkthrough.
Need help connecting?
Read the MCP Guide for the tool reference, or reach out — we'll help you get set up.
Contact support