mcpField
X
Xenmark

Xenmark

Local
xenmark.appProductivity0Updated 8w ago
RepositoryVisit website

About Xenmark

Xenmark is a read-only local MCP server that gives AI assistants access to Xenmark drawing-review data. It uses a user-created token and is limited to the official API and projects the user belongs to.

Key features

  1. 01Read projects and drawing revisions
  2. 02List comments and replies
  3. 03Check the notification inbox
  4. 04Link answers to Xenmark
  5. 05Read-only access to member projects

Use cases

  1. 01Review unresolved drawing comments
  2. 02Check who mentioned you recently
  3. 03Find project roles and revision status

MCP support

It exposes read-only Xenmark project, drawing, revision, comment, reply, and notification data to MCP clients. The local server uses a personal token to connect only to `https://api.xenmark.app`.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "xenmark-xenmark": {
      "command": "npx",
      "args": [
        "-y",
        "xenmark-mcp"
      ],
      "env": {
        "XENMARK_TOKEN": "<XENMARK_TOKEN>"
      }
    }
  }
}
Run commandnpx -y xenmark-mcp
Environment variables to set
XENMARK_TOKENSecretYour Xenmark Personal API token (Postman, GitHub), generated in Xenmark under Account & Security > Connected apps.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmxenmark-mcp0.1.2

Tools

9

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project 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:

{
  "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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.