Connect Claude Code

Claude Code is Anthropic’s command-line coding assistant. Once connected to Mereon, it can look up your company’s processes, policies, and owners while it works, and cite where each answer came from.

1. Add Mereon as an MCP server

   Run this in your terminal:

   claude mcp add --transport http mereon https://api.mereon.ai/v1/mcp

   That registers a server named mereon. There is no token to paste: Mereon uses a browser sign-in instead.

2. Sign in to connect

   Start Claude Code and ask it something about Mereon, such as “search Mereon for our refund policy”. The first time it reaches Mereon it opens your browser. Sign in the way you sign in to the Mereon app, complete multi-factor authentication if your account uses it, choose which organization the connection may read, and approve. Claude Code finishes the request once you approve, and stays connected from then on.

3. Confirm the connection

   Run claude mcp list in Claude Code. Once you have signed in, mereon shows as connected. Before that first sign-in it appears as registered but not yet connected, which is expected.

Headless or CI setup

Running somewhere without a browser? Create a personal access token and pass it as a header instead of signing in:

claude mcp add --transport http mereon https://api.mereon.ai/v1/mcp \
  --header "Authorization: Bearer mrn_..."

Teach it to use Mereon

Tools are only useful if the assistant knows when to reach for them. Drop this into a CLAUDE.md file in your repository so Claude Code consults Mereon before answering questions about how your business works:

## Mereon knowledge base

This organization's business processes, policies, and institutional knowledge
live in Mereon. When you need to know how the business does something (a
process, a policy, who owns an area), use the `search_mereon` tool first, then
`get_topic` / `get_item` to read details and `get_duties` to find owners.
Cite the `url` field of anything you rely on.

Project vs personal scope

By default claude mcp add registers the server for your user. To share the setup with a project’s collaborators, add --scope project, which writes the server to a checked-in config file. With the browser sign-in there is no secret in that file, and each collaborator signs in as themselves and sees their own access. If you use the headless token setup instead, never commit the token: pass it from an environment variable, such as --header "Authorization: Bearer $MEREON_TOKEN".

What it can do once connected

Claude Code gains the full set of Mereon tools: hybrid search, reading a topic or item in full, pulling the text of a source document or transcript, finding who owns a process, and listing data-quality issues, content, and lessons. Everything is read-only and scoped to what you can see in Mereon.

Removing the connection

claude mcp remove mereon

That removes the server from Claude Code. To cut off its access to Mereon, revoke the connection in Profile → Connected apps (or the token in Profile → API Tokens, if you used the headless setup). Revoking takes effect right away.