Skip to content

MCP overview

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data. Mereon runs an MCP server, so any MCP-capable assistant can search and read your knowledge base without you writing any code.

This is the path to choose if you want an assistant like Claude Code or Cursor to answer using your company’s real processes, rather than guessing.

You point your assistant at one URL and connect it. From then on, the assistant has a set of Mereon tools it can call on its own, like search_mereon and get_topic. When you ask it something about how your business works, it looks the answer up in Mereon and cites the source.

  • Endpoint: https://api.mereon.ai/v1/mcp
  • Transport: Streamable HTTP
  • Auth: sign in to connect (a browser sign-in and consent step, recommended for interactive clients), or a personal access token sent as an Authorization: Bearer header for headless use
  • Access: read-only unless you grant more when you connect. A connection granted announcement:write can also draft, send and withdraw announcements, one granted training:assign can assign training and send pop quizzes, one granted lesson:write can create, change, close and split lessons and set the picture they show, one granted content:manage can edit, publish, share and tag your content, including a video or audio transcript, one granted content:delete can delete resources from your library, one granted issue:write can file issues about your knowledge base, one granted public-link:write can share a resource with someone who has no account, one granted content-review:write can approve, reject, or ask for changes on a content submission, and one granted issue:manage can dismiss, reopen, assign, merge and resolve them, and one granted member:manage can invite people, change their organization role, deactivate or reactivate them, remove them, and set who they report to, and one granted team:manage can create, rename and delete teams and change who is on them, and one granted company-role:manage can create a company role, save and publish a draft of its name or description, move, merge and delete it, and choose who holds it and their standing, and one granted duty:manage can assign, change, or remove who is Responsible, Accountable, Consulted, or Informed, including how far a company role’s duty reaches on its advancement path, and one granted curriculum:manage can add or remove a lesson or a topic on a company role’s training curriculum, including when it is due and whether people who already hold the role must take it, and one granted content-grant:manage can grant or remove a video, an audio file, a document, or a guide that an external company role can read, and one granted topic:retire can retire a topic the organization no longer follows and bring it back, and one granted item:retire can retire one item the organization no longer follows and bring it back, and one granted plan:propose can propose a plan of changes that you approve in Mereon before anything runs, and for a solutions partner one granted client:create can create a client organization, as long as you are permitted to. Everything is scoped to exactly what you can see and do in Mereon

Any client that supports a remote, Streamable HTTP MCP server will work. Point it at https://api.mereon.ai/v1/mcp.

Clients that support OAuth for remote MCP servers (Claude Code, Cursor, Claude Desktop, and others) open a browser to sign in and connect the first time they reach Mereon, with no token to configure. For a client that only takes a bearer token, or a headless setup, create a personal access token and set the header:

Authorization: Bearer mrn_...

The exact steps differ per client, but the URL and the tools are the same everywhere.