MCP server for Monnet — motions, plans, files, approvals, and the team's company brain.
Model Context Protocol (MCP) server for Monnet.
Exposes motions, plans, and approvals to MCP-compatible clients (Claude Desktop, Cursor, etc.) so you can work with your Monnet workspace from your terminal without leaving your AI assistant.
Add this to your MCP client config (e.g. ~/Library/Application Support/Claude/claude_desktop_config.json for Claude Desktop):
{
"mcpServers": {
"monnet": {
"command": "npx",
"args": ["-y", "@monnet/mcp"],
"env": {
"MONNET_API_KEY": "mnk_..."
}
}
}
}
Generate an API key at https://app.monnet.ai/settings (API Keys tab).
| Variable | Required | Default | Purpose |
|---|---|---|---|
MONNET_API_KEY | yes | — | API key (mnk_*), sent as the X-API-Key header on every request |
MONNET_API_URL | no | https://api.monnet.ai | Override for self-hosted or local dev backends |
| Tool | Purpose |
|---|---|
monnet_whoami | Verify the connection and list the API keys on your account |
list_workspaces | List the workspaces you belong to |
get_inbox | Fetch your inbox |
list_motions | List motions in a workspace |
get_motion | Read a motion — summary, body, plan, members, comments |
create_motion | Create a new draft motion from a free-form prompt |
update_motion | Update a motion's summary, body, priority, or plan |
comment | Post a comment on a motion (approval-gated, see below) |
approve | Approve a plan step |
reject | Reject a plan step (with an optional reason) |
ask_monnet | Ask Monnet a question on a motion |
Tools that send a message under your identity (e.g. comment) never dispatch automatically. Before the message leaves the MCP server, your client shows a confirmation dialog (MCP elicitation) with a preview; nothing is sent unless you explicitly approve. If your MCP client does not support elicitation, the send is aborted — the gate fails closed.
npm install
npm run build
Point your MCP client at the local build:
{
"mcpServers": {
"monnet": {
"command": "node",
"args": ["/absolute/path/to/monnet-mcp/dist/index.js"],
"env": {
"MONNET_API_KEY": "mnk_...",
"MONNET_API_URL": "http://localhost:8000"
}
}
}
}
Restart your MCP client after editing the config.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @monnet/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"ai-monnet-mcp": {
"command": "npx",
"args": [
"-y",
"@monnet/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@monnet/mcpnpmai.monnet/mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.