
Modusop Mcp
io.github.jwwd-reposPublished by GitHub account jwwd-reposv0.2.5Updated Oct 24, 2026
MCP server for ModusOp — projects, tasks, time tracking, and retainers for AI assistants.
Overview
Stdio proxy that connects MCP clients to ModusOp's Modus Brain, letting an assistant search an organisation's knowledge base and record notes and decisions.
- What you can do
- Identify the user and organisation a token is scoped to
- Search the organisation knowledge base semantically, open a specific result in depth, and list recently indexed items
- Produce a synthesised client one-pager
- Append observations and record decisions with context and rationale, and create typed links between chunks
- Request an admin-gated removal of content
- When to use it
- Useful when your team keeps project, client and decision knowledge in ModusOp's Modus Brain and you want an assistant to retrieve it or add notes while working. Only needed for clients that speak stdio; clients with native remote HTTP MCP can point at the Brain endpoint directly.
- Requirements
- Runs locally via npx from the npm package @modusop/mcp-server, so Node.js is needed. Requires a Brain token from brain.modusop.app supplied in the MODUSOP_API_TOKEN environment variable; MODUSOP_API_URL can override the API base URL. Network access to the ModusOp API is required. Desktop client only.
Installation
In SourceWeft
- Open Modusop Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@modusop/mcp-server
Stdio→HTTP proxy for Modus Brain — gives any MCP-aware AI client (Claude Desktop, Cursor, Cline, Continue.dev, etc.) access to your ModusOp organisation's knowledge base.
What it does
This package is a thin proxy. It speaks the MCP stdio transport on one end and forwards every JSON-RPC request to Modus Brain's HTTP MCP endpoint on the other.
All tool implementations live in Modus Brain itself — when ModusOp ships a new Brain tool, every install of this package picks it up automatically on the next request. No re-publish, no version bump, no user action needed.
If your AI client speaks remote HTTP MCP natively, you don't need this package at all — point it directly at https://brain.modusop.app/mcp. This package exists for clients that only speak stdio.
Setup
1. Get a Brain token
Sign in at brain.modusop.app, generate a token labelled for the device or person who'll use it, copy the plaintext value (you only see it once).
2. Add to your AI client's MCP config
Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Cursor / Cline / Continue.dev — .cursor/mcp.json (or the equivalent):
3. Restart your client
Quit and reopen. The Modus Brain tools should appear in the MCP indicator within a few seconds.
Env vars
Available tools
Whatever Brain exposes — tools/list reflects the current set. As of v1.0.0:
whoami— identify the user + org this token is scoped tosearch_knowledge— semantic search over the org KBget_chunk— deep-dive on a specific search resultlist_recent— recently indexed KB itemsget_client_brief— synthesised client one-pageradd_observation— append a noteadd_decision— record context + decision + rationalelink_observation— typed link between two chunksrequest_delete— admin-gated removal
Migrating from 0.x
Versions 0.x of this package implemented tools in-package and talked to ModusOp's older /api/mcp endpoint with an MO API token from /settings/api-tokens. v1.0.0 retires that path:
- Generate a new Brain token at brain.modusop.app, not an MO API token
- Replace the value of
MODUSOP_API_TOKENwith the new token - No other config change needed — same
command, sameargs, same env var name
Old tools (search_projects, search_clients, get_client_context, start_timer, etc.) are no longer present in this package's catalogue. They've been retired in favour of Brain's tools, which cover the same surface plus knowledge-base search and append-writes. If you need the old tool set, pin to @modusop/[email protected] — it still works but won't receive updates.
Local development
The proxy reads JSON-RPC on stdin and writes responses on stdout, so test it manually with:
Licence
See LICENSE.md.
Source: README.md at commit f744cbd
Tools
0Version history
1- v0.2.5LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.