Search DevTools

Jump to any tool or page

mcp

MCP server for Monnet — motions, plans, files, approvals, and the team's company brain.

GregoireCasoetto0 stars0 forksDeveloper Tools
View source

Install

Terminal

$npx -y @monnet/mcp

mcp_config.json

{
  "mcpServers": {
    "ai-monnet-mcp": {
      "env": {
        "MONNET_API_KEY": "${MONNET_API_KEY}"
      },
      "args": [
        "-y",
        "@monnet/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

@monnet/mcp

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.

Install

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).

Environment variables

VariableRequiredDefaultPurpose
MONNET_API_KEYyes—API key (mnk_*), sent as the X-API-Key header on every request
MONNET_API_URLnohttps://api.monnet.aiOverride for self-hosted or local dev backends

Tools

ToolPurpose
monnet_whoamiVerify the connection and list the API keys on your account
list_workspacesList the workspaces you belong to
get_inboxFetch your inbox
list_motionsList motions in a workspace
get_motionRead a motion — summary, body, plan, members, comments
create_motionCreate a new draft motion from a free-form prompt
update_motionUpdate a motion's summary, body, priority, or plan
commentPost a comment on a motion (approval-gated, see below)
approveApprove a plan step
rejectReject a plan step (with an optional reason)
ask_monnetAsk Monnet a question on a motion

Approval gate on send actions

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.

Local development

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.

License

MIT

Sourced from the repository README.

More in Developer Tools