Server data from the Official MCP Registry
Model Context Protocol server for Monnet — motions, plans, and approvals for MCP-compatible clients.
Model Context Protocol server for Monnet — motions, plans, and approvals for MCP-compatible clients.
Well-structured MCP server with proper authentication, reasonable input validation, and appropriate security controls including approval gating for sensitive operations. API key authentication is correctly handled through environment variables, and the approval mechanism ensures user consent before sending messages on their behalf. Minor code quality observations present but do not materially impact security. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
7 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: MONNET_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"ai-monnet-mcp": {
"env": {
"MONNET_API_KEY": "your-monnet-api-key-here"
},
"args": [
"-y",
"@monnet/mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.