Connect Claude Code to OrgRelay

One command adds the company's OrgRelay to Claude Code. After that, you can ask about company documents, tables and connected systems from the terminal, with the same permissions you have in OrgRelay's app.

You need a personal token from My account → MCP connections in OrgRelay; the MCP overview explains how to get one. Replace https://ai.example.com with your company's OrgRelay address.

#Remote connection (recommended)

Works from any computer that can reach the OrgRelay address.

claude mcp add --transport http orgrelay https://ai.example.com/mcp \
  --header "Authorization: Bearer <your-token>"

Check it:

claude mcp list

orgrelay ... ✔ Connected means you are set. Inside Claude Code, /mcp shows the same status and lists the tools.

Then ask normally, naming the server so Claude picks the right tools:

Use orgrelay to check this month's receivables for customers in East China. Cite sources.

#Local connection (stdio)

For use on the Mac mini that runs OrgRelay, or on networks that only allow local processes. OrgRelay serves a small bridge script:

curl -fsSL https://ai.example.com/mcp/orgrelay-mcp.mjs -o ~/orgrelay-mcp.mjs
claude mcp add orgrelay \
  --env ORGRELAY_URL=https://ai.example.com/mcp \
  --env ORGRELAY_TOKEN=<your-token> \
  -- node ~/orgrelay-mcp.mjs

On the Mac mini itself the URL can be http://127.0.0.1:8686/mcp. The bridge needs Node.js 18 or later.

#Scopes

Claude Code stores servers in one of three scopes:

For a shared project, reference an environment variable so the token stays out of the repository:

{
  "mcpServers": {
    "orgrelay": {
      "type": "http",
      "url": "https://ai.example.com/mcp",
      "headers": { "Authorization": "Bearer ${ORGRELAY_TOKEN}" }
    }
  }
}

Each teammate sets ORGRELAY_TOKEN to their own token. Tokens are personal; sharing one breaks the audit trail and OrgRelay's account rules.

#Make answers cite sources

Add OrgRelay's recommended system prompt, shown on the MCP overview, to your CLAUDE.md. It tells Claude to search before answering, to compute numbers with query_table and to propose changes only through create_approval_request.

#A quick permission check

Ask two questions after connecting:

1. "Use orgrelay to find how payment terms are written in our recent quotations, with sources." You should see file names and locations.
2. With an ordinary employee's token: "Use orgrelay to list salaries in the finance folder." The answer must be that nothing is accessible.

Permissions are enforced on the OrgRelay server, not by the model. The details are on enterprise MCP patterns.

#Using Claude Code to build connectors

Claude Code is also a convenient test client while you develop a connector. Add your connector the same way, pointing at http://127.0.0.1:8787/mcp with a test token, and call its tools before involving OrgRelay. The quickstart and the MCP transport spec cover the server side; the self-test tool gives the formal pass or fail.

#Troubleshooting

#Common questions

User or project scope? User scope for personal use. Project scope only with an environment variable for the token.

Failed to connect? Check the address in a browser, Cloudflare Access, then the token.

Can Claude Code approve? No. It can only create approval requests.

#Next

• Other clients: Claude Desktop and claude.ai, Codex, Cursor.
• Why approvals stay in OrgRelay: human-in-the-loop for MCP.
• Teams deciding whether staff should use their own AI clients can read the business side on orgrelay.com/security.
• Tools from systems the owner has connected, such as WooCommerce or QuickBooks Online, appear next to OrgRelay's own, limited to your role.
• Company know-how packaged as Agent Skills is available through the same connection.
• Security rules every connector follows: security requirements.
• Vendor MCP servers you might otherwise add to Claude Code directly: official MCP servers.

#Related pages

• Connector spec: manifest fields, naming, errors, paging and versioning.
• Approvals and write tools: idempotency keys and re-checks for write tools.
• Authentication: tokens, OAuth client credentials and rotation.
• Code templates: download the developer kit and four templates.