Xenmark

io.github.XenmarkPublished by GitHub account Xenmarkv0.1.2Updated Oct 27, 2026

Read your Xenmark drawing reviews from AI assistants: projects, drawings, comments, notifications.

Overview

AI-generated overview

Read-only MCP server that lets an AI assistant browse your Xenmark drawing-review projects, drawings, revisions, comments and notifications.

What you can do
  • List the projects you belong to and your role in each
  • Browse drawings and revisions, including what is still open on a given revision
  • Read comments and replies, including unresolved ones and who raised them
  • Check your notification inbox for new items and mentions
  • Return links back into Xenmark with each answer
When to use it
Useful if you review drawings in Xenmark and want to ask an assistant about open comments, revision status, project membership or new mentions without opening the app. It is read-only, so it is for looking things up rather than changing review data.
Requirements
Runs locally over stdio via npx, requiring Node.js 18 or newer. Needs a Xenmark Personal API token supplied in the XENMARK_TOKEN environment variable, generated in Xenmark under Account & Security > Connected apps. Network access to the Xenmark Integration API is required. Desktop assistants only.
Before you install
The Xenmark token is a live credential stored in the assistant's config; keep it out of shared files and revoke it from Connected apps if exposed. The server is described as read-only and scoped to projects you are a member of, but your review data is sent to the Xenmark API and surfaced to the assistant and its model provider.

Installation

In SourceWeft

  1. Open Xenmark in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Xenmark MCP server

An MCP server that lets AI assistants — Claude, Cursor, VS Code and others — read your Xenmark drawing-review data: projects, drawings, revisions, comments, replies and your notification inbox. Read-only, runs on your own machine, uses a token you create inside Xenmark.

Status: released. On npm as xenmark-mcp and in the official MCP Registry as io.github.Xenmark/xenmark-mcp.

What you can ask

  • "Anything new for me in Xenmark?" / "Who mentioned me today?"
  • "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?"

Every answer carries a link straight into Xenmark.

What it never does

It never writes to Xenmark, never sees your password, never returns e-mail addresses, files, billing or account roles, and never reaches projects you are not a member of. It talks to exactly one server: https://api.xenmark.app, the official read-only Integration API (contract).

Get a token

In Xenmark: profile → Account & Security → Connected apps → Connect an app → "Personal API token (Postman, GitHub)" → Generate. The token is shown once; keep it in the assistant's config only. Revoke it any time from Connected apps.

Install

Requires Node.js 18 or newer. The server runs with npx -y xenmark-mcp — nothing to clone or build. (To run from a source checkout instead: npm install && npm run build, then point your assistant at dist/index.js.)

Claude Desktop — edit claude_desktop_config.json (Settings → Developer → Edit Config) and add:

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

Restart Claude Desktop; the Xenmark tools appear under the tools icon.

Cursor — Settings → MCP → Add new server, same command, args and env.

VS Code (Copilot agent mode) — add the same entry under "servers" in .vscode/mcp.json or your user mcp.json.

From a source checkout, replace the command with node and the args with the full path to dist/index.js.

Support

[email protected] · Security: see SECURITY.md. Never post a token anywhere public.

Source: README.md at commit 404a5cf

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts