@papermark/mcp-server

Model Context Protocol server for Papermark. Exposes your data rooms — plus documents, share links, visitors, and analytics — as tools any MCP-compliant client can call (Claude Desktop, Claude Code, ChatGPT, Cursor, Zed, Continue, Windsurf, …).

Quick start — stdio mode (local)

1. Create an API token at papermark.com/settings/tokens (or via papermark login in the CLI, which stores one to ~/Library/Preferences/papermark-nodejs/config.json on macOS).

2. Add this to your MCP client config. For Claude Desktop, ~/Library/Application Support/Claude/claude_desktop_config.json:

   {
     "mcpServers": {
       "papermark": {
         "command": "npx",
         "args": ["-y", "@papermark/mcp-server"],
         "env": { "PAPERMARK_TOKEN": "pm_live_xxx" }
       }
     }
   }

3. Restart the MCP client. Ask it something like "List my Papermark data rooms" — it'll call list_datarooms and stream the result back.

To run locally against a dev API instead of production:

{ "env": {
  "PAPERMARK_TOKEN": "pm_live_xxx",
  "PAPERMARK_API_URL": "http://localhost:3000/api"
} }

Smoke test

PAPERMARK_TOKEN=pm_live_xxx npm run smoke

Walks the stdio server through initialize, tools/list, a tools/call success, and an error path — useful for verifying a local build before pointing a client at it.

Tools

• list_documents, get_document, search_documents, upload_document
• list_links, create_link, list_link_views
• list_datarooms, search_datarooms, get_dataroom, create_dataroom, list_dataroom_documents
• list_visitors, list_visitor_views
• get_document_analytics, get_link_analytics, get_dataroom_analytics, get_view_analytics

Environment

• PAPERMARK_TOKEN — bearer token (required for stdio mode)
• PAPERMARK_API_URL — override the API base (default https://api.papermark.com)

Remote deployment

A hosted version is available at mcp.papermark.com using Streamable HTTP transport and OAuth 2.1.

License

MIT