Claude Web & Mobile

Connect Crow to Claude on the web (claude.ai) or the Claude mobile app using Custom Integrations.

Prerequisites

• Crow gateway deployed and healthy (Cloud Deploy Guide)
• A Claude Pro, Team, or Enterprise plan (Custom Integrations require a paid plan)

Setup Steps

1. Go to claude.ai/settings → Integrations
2. Click Add Custom Integration
3. Enter a name (e.g., "Crow Memory")
4. Paste your gateway URL:

   https://your-crow-server/memory/mcp

5. Click Save — Claude will initiate the OAuth flow
6. Authorize the connection when prompted

Repeat for each server you want to connect:

Server	URL
Memory	https://your-crow-server/memory/mcp
Projects	https://your-crow-server/projects/mcp
Sharing	https://your-crow-server/sharing/mcp
Storage	https://your-crow-server/storage/mcp
Blog	https://your-crow-server/blog-mcp/mcp
External Tools	https://your-crow-server/tools/mcp

Note: The storage endpoint requires MinIO to be configured. See the Storage Guide for setup.

Transport

• Type: Streamable HTTP
• Protocol: 2025-03-26
• Auth: OAuth 2.1 (automatic)

Self-Hosted / Local Setup

If you're running the Crow gateway on your own machine (e.g., a Raspberry Pi or home server), you can expose it to Claude using Tailscale Funnel. Once Funnel is enabled on the machine running the gateway, your MCP endpoint URL will be:

https://<hostname>.<tailnet>.ts.net/memory/mcp

Replace <hostname> and <tailnet> with your Tailscale machine name and tailnet domain. Use the same URL pattern for other servers (/projects/mcp, /router/mcp, etc.). The OAuth flow and setup steps are identical to the cloud instructions above — just substitute your Funnel URL for your-crow-server.

See the Tailscale Setup guide for full configuration details.

Verification

After connecting, try asking Claude:

"Store a memory that Crow is now connected."

If it works, you'll see Crow's memory tools in action. You can verify stored memories by asking:

"What do you remember?"

Troubleshooting OAuth

If the connector fails to connect or tools don't appear:

• Leave OAuth Client ID and Client Secret blank. Crow uses Dynamic Client Registration (RFC 7591) — Claude discovers the OAuth endpoints automatically from the .well-known metadata. No pre-configured credentials needed.
• Verify your gateway's OAuth metadata is reachable. Visit https://your-crow-server/.well-known/oauth-authorization-server in your browser — you should see a JSON response with authorization_endpoint, token_endpoint, and registration_endpoint.
• Check CROW_GATEWAY_URL in your .env file. This must match your actual public URL exactly (including https://). If you're using Tailscale Funnel, it should be https://<hostname>.<tailnet>.ts.net.
• Start a new conversation after gateway restarts. OAuth sessions are tied to the gateway process. When the gateway restarts, existing Claude.ai sessions become invalid — start a fresh conversation to re-authenticate.
• Check gateway logs for OAuth errors. If running via systemd: journalctl -u crow-gateway -f. Look for errors in the /register, /authorize, or /token endpoints.

Cross-Platform Context

Crow automatically delivers behavioral context during the MCP connection handshake. When Claude connects to any Crow server, it receives Crow's identity, memory protocols, session protocol, transparency rules, and capability reference — no user action required.

This means Claude knows to recall relevant memories at the start of each conversation, store important information, and follow transparency rules from the very first message.

For deeper guidance, Claude can request MCP prompts:

• session-start — Detailed session start/end protocol
• crow-guide — Full crow.md document with all behavioral sections
• research-guide / blog-guide / sharing-guide — Workflow guidance for specific features

These prompts serve as skill equivalents, giving Claude detailed workflow instructions on demand without consuming context window space upfront.

You can also manually load the full context:

"Load your crow.md context"

See the Cross-Platform Guide for more details.

Context Optimization

Claude Code supports toolListChanged notifications, making crow-core a good fit for local use — it activates servers on demand rather than loading all tools upfront.

For Claude via the gateway, the /router/mcp endpoint reduces the tool count from 49+ to 7 consolidated category tools, significantly reducing context window usage. Instead of connecting each server individually, you can connect a single router endpoint:

https://your-crow-server/router/mcp

See the Context & Performance guide for more details.

Shared with Claude Code CLI

Custom Integrations you add here are also available in Claude Code CLI sessions — they share the same connector configuration within Anthropic's ecosystem. If you set up Crow on claude.ai, it works in Claude Code without additional setup. This cross-platform sharing is specific to Claude; other platforms (ChatGPT, Gemini) manage their MCP connections independently.

Tips

• You can connect all five servers (memory, projects, sharing, storage, blog) plus external tools simultaneously
• The mobile app uses the same Custom Integrations as the web
• Tools from external integrations (GitHub, Slack, etc.) appear through the /tools/mcp endpoint
• Memories stored here are instantly accessible from ChatGPT, Gemini, or any other connected platform