MCP server

The Monnet MCP server exposes your workspace — motions, inbox, comments, approvals, and your whole company brain — to any client that speaks the Model Context Protocol. Read, draft, and act on your team’s work from your coding agent.

For your first setup, start with the web quickstart. The MCP server is optional: connect it when you want to work with Monnet from a coding agent. You can still use the guided CLI setup below to get started.

Before you start

You need:

Node.js 20 or newer.
Claude Code or Codex for the guided setup.

You don’t need to create a Monnet account, workspace, or API key first. The guided setup handles sign-up or sign-in and helps you create or join a workspace.

Install

Run this once from your terminal:

npx -y @monnet/mcp install

This installs the Monnet MCP server and its guided onboarding command for both Claude Code and Codex. Next, quit your coding agent completely and reopen it. Starting a new session inside the running app is not enough. Then run:

Claude Code
Codex

/monnet-init

$monnet-init

See Onboarding for what the guided setup does and how to resume it if interrupted.

Manual configuration

For Claude Desktop, Cursor, or another MCP-compatible client, generate an API key in Settings and add the server to your client’s MCP configuration:

{
  "mcpServers": {
    "monnet": {
      "command": "npx",
      "args": ["-y", "@monnet/mcp@latest"],
      "env": {
        "MONNET_API_KEY": "<YOUR_KEY>"
      }
    }
  }
}

Common configuration file locations:

Claude Desktop on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Claude Desktop on Windows: %APPDATA%\Claude\claude_desktop_config.json
Cursor: ~/.cursor/mcp.json

Restart the client after saving the configuration.

Treat an API key like a password. Anyone with it can read and modify motions on your behalf. Revoke a key from Settings → Monnet MCP if it ever leaks.

Verify the connection

Ask your assistant:

Use the monnet_whoami tool to confirm the connection.

It returns your account details and the API keys attached to your account. If a manually configured client gets an authentication error, double-check the MONNET_API_KEY value in its config.

Uninstall

npx -y @monnet/mcp uninstall

This removes Monnet from Claude Code and Codex, removes the guided onboarding command, deletes the credential saved on this machine, and revokes its API key. If the key cannot be revoked, the command tells you how to revoke it from Settings → Monnet MCP.

Environment variables

Variable	Required	Default	Purpose
`MONNET_API_KEY`	no	Credential saved by the guided setup	API key sent on every request. Set this when configuring a client manually.
`MONNET_API_URL`	no	`https://api.monnet.ai`	Override the backend URL — useful for self-hosted or local setups.

Available tools

Workspaces and motions

Tool	Purpose
`monnet_whoami`	Verify the connection and list the API keys on your account.
`list_workspaces`	List the workspaces you belong to, with their names and slugs.
`list_motions`	List motions in a workspace, filterable by status.
`get_motion`	Read a motion in full — summary, document, status, priority, plan, members, comments, files.
`update_motion`	Update a motion’s summary, document, priority, or plan.
`read_motion_file`	Read a file attached to a motion.
`get_inbox`	Fetch your feed — motions across your workspaces that need attention.

Taking part

Tool	Purpose
`create_thread`	Open a conversation with Monnet about an idea.
`comment`	Post a public comment on a motion.
`approve`	Approve a plan step.
`reject`	Reject a plan step, with an optional reason.
`ask_monnet`	Ask Monnet a question in the context of a specific motion.

Playbooks

Tool	Purpose
`list_playbooks`	List the reusable workflow instructions in a workspace.
`create_playbook`	Add a playbook for a recurring workflow.
`edit_playbook`	Revise an existing playbook.

Company brain

Tool	Purpose
`get_wiki_schema`	Read the rules your team’s brain is organized by.
`get_wiki_tree`	List every folder and page, with their ids.
`read_wiki_page`	Read one page in full.
`search_wiki`	Search across pages.
`create_wiki_page` / `edit_wiki_page` / `delete_wiki_page`	Write, correct, or remove a page.
`create_wiki_folder` / `rename_wiki_folder` / `delete_wiki_folder`	Organize the tree.
`move_wiki_node`	Move a page or folder.
`list_wiki_sources` / `read_wiki_source` / `push_wiki_source`	Browse, read, and add the raw material behind the brain.
`mark_wiki_source_ingested` / `requeue_wiki_source` / `delete_wiki_source`	Control what the nightly ingest picks up.

Two habits the server asks for. Read before you write — get_motion before updating one, get_wiki_tree before deciding a subject has no page, get_wiki_schema before your first write to a workspace’s brain. And anything a person will see, or can’t take back, is theirs to approve — comment, edit_playbook, and the delete tools stop and ask you out of band before they act.

create_motion and get_workspace_memory no longer exist. Use create_thread — an idea starts as a conversation and becomes a motion when it needs other people — and the wiki tools, since workspace memory became the company brain.

Troubleshooting

The monnet tools don't appear in my client

Quit the client completely and reopen it. A new session inside an already-running app will not pick up the server. In Claude Desktop, check Help → Logs for MCP-related errors.

I get a 401 / authentication error

Run the guided onboarding command again in Claude Code or Codex. For a manually configured client, the API key is missing, wrong, or revoked; generate a fresh key and update your config.

npx hangs or fails to install

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.

One tool fails while the others work

Almost always a stale copy of the server: npx happily reuses a cached old version. Pin @monnet/mcp@latest in your config, or clear the npx cache, and restart the client.

Getting started

Concepts

Product

Integrations

Before you start

Install

Manual configuration

Verify the connection

Uninstall

Environment variables

Available tools

Workspaces and motions

Taking part

Playbooks

Company brain

Troubleshooting

​Before you start

​Install

​Manual configuration

​Verify the connection

​Uninstall

​Environment variables

​Available tools

​Workspaces and motions

​Taking part

​Playbooks

​Company brain

​Troubleshooting

Before you start

Install

Manual configuration

Verify the connection

Uninstall

Environment variables

Available tools

Workspaces and motions

Taking part

Playbooks

Company brain

Troubleshooting