Mcp

Model Context Protocol server for Monnet — motions, plans, and approvals for MCP-compatible clients.

Mcp is a Model Context Protocol server published by ai.monnet under the package @monnet/mcp (version 0.2.3 on npm). It connects MCP-compatible clients to Monnet, a platform centred on motions, plans, and approvals workflows. The server communicates over stdio transport and requires a MONNET_API_KEY environment variable to authenticate with the Monnet API.

Because no tool definitions are exposed in the registry record, the exact set of callable operations cannot be enumerated here. Based on the server’s stated purpose — motions, plans, and approvals — agents connecting to it can be expected to interact with structured decision or workflow objects in Monnet: creating or retrieving motions, managing plans, and processing approval steps. These are the kinds of operations relevant to governance, planning, or review workflows where structured human or automated sign-off is required.

The server runs over stdio, which means it is suitable for local process-based integrations and single-machine deployments. Remote or HTTP-based transport is not indicated by the available facts. A valid Monnet API key must be available as an environment variable before the server can connect to the Monnet backend.

Use cases

  • Integrate Monnet motion and approval workflows into an MCP-compatible AI agent pipeline
  • Automate retrieval or creation of plans stored in Monnet via an agent
  • Route approval steps in a Monnet workflow through an AI orchestration layer
  • Connect a local MCP client to a Monnet account using an API key

When to use it

  • The agent or orchestration system already uses MCP-compatible tooling
  • The workflow involves Monnet motions, plans, or approvals
  • A stdio-based local transport is acceptable for the deployment

When not to use it

  • No Monnet account or API key is available — authentication is required
  • The integration requires HTTP or SSE transport rather than stdio
  • The use case has no relation to Monnet's motions, plans, or approvals domain
  • A full enumeration of available tools is needed before adoption — none are listed in the registry record