MCP
MCP: tools, clients and connections
The tools Growth OX offers to any MCP client, how to add the server to your AI tool, and how Growth OX reaches the services you connect. Generated from the server and the configuration.
What the server is#
The server runs on your computer and talks to one AI tool over standard input and output, using JSON-RPC. It answers four requests: initialize, ping, list the tools and call a tool. It offers tools only. It starts when your AI tool starts it and stops with it.
The server believes the user name it is started with. It keeps people apart on one computer as a convenience; it is not a sign-in. A tool result has a size limit, and a larger answer is refused so the model asks for less.
The start options can limit a server to a list of tools, a note class and a language. A client that should only search can be given only the search tools.
Tools#
One table per family. Each row shows the tool name, what it does and its arguments. Arguments marked optional can be left out. The descriptions are the server's own text.
| Tool | What it does | Arguments |
|---|---|---|
agent_speak | Ask the person's computer to say one short sentence aloud in the voice the person gave you. | text, lang (optional) |
| Tool | What it does | Arguments |
|---|---|---|
brain_changes | What other agents and people changed since you last looked. | since (optional), limit (optional), peek (optional) |
brain_get | Step 3 of 3. | id, project |
brain_search | Step 1 of 3. | query, project, types (optional), limit (optional), include_history (optional), as_of (optional), known_at (optional), include_retired (optional) |
brain_summary | Call once at the start of a session: goals, the notes most relevant to your query, open handoffs and changes since your last look, sized for your model. | query (optional), project, goal (optional), accept_open (optional) |
brain_timeline | Step 2 of 3. | id, project, before (optional), after (optional), mode (optional) |
brain_write | Propose a note (decision, bugfix, finding, preference, learning, fact). | kind, title, body_md, project, lang (optional) |
| Tool | What it does | Arguments |
|---|---|---|
device_models_preview | Read-only. | device, change |
device_models_propose | Ask for a change of one device's model profile (dial, rows, clear or revert). | device, change, note (optional) |
device_models_show | Read-only. | device (optional) |
| Tool | What it does | Arguments |
|---|---|---|
engine_switch_list | Read-only. | none |
engine_switch_preview | Read-only. | engine, groups (optional), scope (optional) |
engine_switch_propose | Ask for an engine change. | engine, groups (optional), scope (optional), note (optional) |
| Tool | What it does | Arguments |
|---|---|---|
handoff_accept | Take an open handoff addressed to you. | id |
handoff_close | Finish a handoff you accepted (outcome done), or mark one as replaced by a newer handoff (outcome superseded, superseded_by required). | id, outcome, note (optional), superseded_by (optional) |
handoff_list | List handoffs from other agents (default: open and accepted). | id (optional), status (optional), goal (optional) |
handoff_open | Hand the work to another agent. | goal (optional), to_agent (optional), to_role (optional), repo (optional), done (optional), next, open_questions (optional), constraints (optional), artifacts (optional), citations (optional), body (optional) |
| Tool | What it does | Arguments |
|---|---|---|
skill_get | Read-only. | project, name |
Add it to your AI tool#
The app can write the entry for you from the connections screen. If you prefer to do it by hand, these are the configuration files each tool reads. The entry names the Growth OX server command and your user name.
| AI tool | macOS | Windows | Linux |
|---|---|---|---|
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json | %APPDATA%/Claude/claude_desktop_config.json | ~/.config/Claude/claude_desktop_config.json |
| Claude Code | ~/.claude.json | ~/.claude.json | ~/.claude.json |
| Codex | ~/.codex/config.toml | ~/.codex/config.toml | ~/.codex/config.toml |
| Cursor | ~/.cursor/mcp.json | ~/.cursor/mcp.json | ~/.cursor/mcp.json |
| Google Gemini | ~/.gemini/settings.json | ~/.gemini/settings.json | ~/.gemini/settings.json |
| Windsurf | ~/.config/devin/mcp_config.json | %APPDATA%/devin/mcp_config.json | ~/.config/devin/mcp_config.json |
| OpenCode | ~/.config/opencode/opencode.json | ~/.config/opencode/opencode.json | ~/.config/opencode/opencode.json |
| GitHub Copilot (VS Code) | ~/Library/Application Support/Code/User/mcp.json | %APPDATA%/Code/User/mcp.json | ~/.config/Code/User/mcp.json |
A path the tool's own documentation does not state for an operating system is marked unconfirmed in the configuration and still needs a check on a real machine.
Bring your own MCP server#
A service you already reach through an MCP server does not need a second setup. Growth OX tries the ways below in this order for each service and uses the first one that is ready. A way whose precondition is missing is hidden, and the next one is tried.
| Way in | What it is |
|---|---|
| Your connected AI | The AI you already connected, through its own official command-line tool |
| Already installed | A tool, command-line tool or MCP server that is already on this computer |
| Existing MCP definition | An MCP server definition that another app already holds. Growth OX reads the definition and never holds a secret value from it |
| Remote MCP | The vendor's remote MCP server, with the vendor's sign-in |
| Native sign-in | A public Growth OX sign-in client that returns to a local address on your computer |
| Vendor command line | A vendor command-line tool you are already signed in to |
| Your browser | Your own browser, through the Growth OX extension |
| Local export | Local data and export files you pick |
| API carrier | A model vendor's connector, using your own API key; every call needs your approval |
| Your aggregator | Your own Composio, Pipedream or Zapier account |
| Manual setup | Steps shown on screen for you to do by hand |
- Open the connections screen in the app and choose the service.
- Growth OX shows the best way that is ready and what each other way would need from you.
- If you bring your own MCP server, allow the project folder or app configuration that holds it. Growth OX reads the server definition from there.
- Sign in if the way needs it. The sign-in happens at the vendor, not in Growth OX.
- Anything that sends, posts or changes something outside your computer still waits for your approval.
Every service and tool group is listed on the integrations page, with the ways that exist for it.
Limits and safety#
- Tools whose names end in propose only leave a proposal. You review it in the app before anything changes. See Approvals.
- A start option sets the highest class of notes a route may receive.
- What the server sends out is covered by What leaves your computer.
- How the work is verified is described in How Growth OX checks its work.
Questions#
- Does the MCP server need an internet connection?
- No. It runs on your computer and answers the tool that started it. A tool you add may use the internet for its own work; that is the tool's own traffic.
- Can a client change my notes?
- Only through the write tools in the table. A client you start with a restricted tool list cannot call the others.
- Where do I find the tool list for my own client?
- Ask the client for the tools of the Growth OX server. The names are the ones in the table on this page.