AI assistants (MCP)

https://api.norreach.app/mcp is a Model Context Protocol server: the API operations as tools an AI assistant can use, with the same API keys, scopes and rules. Streamable HTTP, stateless, one JSON answer per request. Authenticate with an API key as a bearer token — or, for chat assistants, with OAuth (see Connect a chat assistant).

Install

One command or one click adds the server https://api.norreach.app/mcp. You then sign in to NorReach in your browser and choose what the assistant may do (OAuth) — or send an API key instead.

Claude Code

claude mcp add --transport http norreach https://api.norreach.app/mcp

Then run /mcp in Claude Code, pick norreach and authenticate: NorReach opens in your browser.

Cursor

Add to Cursor — or put this in ~/.cursor/mcp.json, and Cursor asks you to sign in:

{
  "mcpServers": {
    "norreach": {
      "url": "https://api.norreach.app/mcp"
    }
  }
}

VS Code

Add to VS Code — or from the command line:

code --add-mcp '{"name":"norreach","type":"http","url":"https://api.norreach.app/mcp"}'

With an API key instead

claude mcp add --transport http norreach https://api.norreach.app/mcp --header "Authorization: Bearer nr_live_…"

In other clients, add the header Authorization: Bearer nr_live_… to the server (below). With a key there is no sign-in: the assistant acts as the key's creator, within the key's scopes.

Connect a client

Clients that take a URL and headers

Most editor and desktop assistants: add a server of type HTTP (Streamable HTTP) with the URL and an Authorization header.

{
  "mcpServers": {
    "norreach": {
      "type": "http",
      "url": "https://api.norreach.app/mcp",
      "headers": { "Authorization": "Bearer nr_live_…" }
    }
  }
}

Cursor

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "norreach": {
      "url": "https://api.norreach.app/mcp",
      "headers": { "Authorization": "Bearer nr_live_…" }
    }
  }
}

Clients without custom headers

npx mcp-remote https://api.norreach.app/mcp --header "Authorization: Bearer $NORREACH_API_KEY"

Chat assistants that connect with a sign-in instead of a key (custom connectors) use OAuth — see Connect a chat assistant. Developers building their own client: OAuth with the resource https://api.norreach.app/mcp.

What it offers

• Tools — one per operation the key may run (see the tool list). A key with only read scopes gets only read tools.
• Resources — norreach://docs/overview, norreach://docs/approvals-and-sends, norreach://docs/errors, norreach://docs/webhooks, norreach://workspace/summary and norreach://contacts/{id}.
• Prompts — daily_briefing, triage_approvals, follow_up_new_leads, campaign_report.

A tool call runs the same operation as the REST API — the same checks, limits, idempotency and audit log (recorded as made through the MCP server with your key, or by you through the connected app).