Skip to main content
The Monnet MCP server exposes your workspace — motions, inbox, comments, approvals — to any client that speaks the Model Context Protocol. Read, draft, and act on motions from your coding agent.

Before you start

You need:
  • A Monnet account with at least one workspace.
  • A Monnet API key — generate one in Settings.
  • An MCP-compatible client: Claude Code, Claude Desktop, Cursor, or Codex.
Treat your API key like a password. Anyone with it can read and modify motions on your behalf. Revoke a key from Settings if it ever leaks.

Install

Run:
claude mcp add monnet -e MONNET_API_KEY=<YOUR_KEY> -- npx -y @monnet/mcp
Restart Claude Code to pick up the new server.

Verify the connection

Ask your assistant:
Use the monnet_whoami tool to confirm the connection.
It returns your account details and the list of API keys attached to your account. If you get an authentication error, double-check the MONNET_API_KEY value in your config.

Environment variables

VariableRequiredDefaultPurpose
MONNET_API_KEYyesYour Monnet API key. Sent on every request.
MONNET_API_URLnohttps://api.monnet.aiOverride the backend URL — useful for self-hosted or local setups.

Available tools

ToolPurpose
monnet_whoamiVerify the connection and list the API keys on your account.
More tools — list_motions, get_motion, create_motion, comment, approve — are in development. This page updates as they ship.

Troubleshooting

Make sure you restarted the client after editing the config. In Claude Desktop, check Help → Logs for MCP-related errors.
The API key is missing, wrong, or revoked. Generate a fresh key in Settings and update your config.
Check your Node.js version — the MCP server requires Node 20 or newer. Run node --version to confirm. If you use nvm or fnm, make sure the right version is active in the shell your MCP client inherits.