Xenmark/Docs /How to connect an AI assistant to Xenmark — review guide

How to connect an AI assistant to Xenmark

Xenmark MCP is a small open-source server that connects an AI assistant to your Xenmark reviews. Ask what is new, what is still open on a revision, or who replied to what, and the answer comes back with links into Xenmark. It runs on your own machine and cannot write anything. Free on every plan.

Updated 4 September 2026

Xenmark MCP is a small open-source server that connects an AI assistant to your Xenmark reviews. Once it is installed you can ask questions in plain language and get answers that link straight back into the review.

It works with any assistant that speaks the Model Context Protocol — Claude Desktop, Cursor and VS Code among them — and it is free on every plan.

What you can ask

  • “Anything new for me in Xenmark?”
  • “Which projects am I on, and what’s my role?”
  • “What’s still open on drawing 1001-300, Rev. B?”
  • “List the unresolved comments on that revision and who raised them.”
  • “What did Greta reply on comment #7?”

The assistant reads your inbox, revisions, summaries and comments through the API, works out the answer, and gives it to you with a link into Xenmark for every item it mentions — so you go straight to the comment instead of hunting for it.

What you need

Install it

Add one entry to your assistant’s MCP configuration. For Claude Desktop that is claude_desktop_config.json, reachable from Settings → Developer → Edit Config:

{
  "mcpServers": {
    "xenmark": {
      "command": "npx",
      "args": ["-y", "xenmark-mcp"],
      "env": { "XENMARK_TOKEN": "xmk_live_YOUR_TOKEN_HERE" }
    }
  }
}

Restart the assistant and the Xenmark tools appear. Cursor and VS Code take the same entry in their own MCP settings.

What it can and cannot do

The server exposes nine read-only tools covering identity, recent activity, projects, drawings, revisions, review summaries, comments, replies, and drawing search.

It runs on your own machine, talks to exactly one server — api.xenmark.app — and stores nothing. It cannot write to Xenmark, because the Integration API it reads through cannot either. No assistant can create a comment, change a status or upload a drawing on your behalf.

The token lives in your assistant’s configuration file and nowhere else. Revoking it under Connected apps stops the server immediately.

Where to find it

The server is published on GitHub under the MIT licence, on npm as xenmark-mcp, and in the official MCP Registry as io.github.Xenmark/xenmark-mcp. All three are linked from the Integrations & API page, along with the full installation notes and security details.

Related