CLI

MCP server

Let Claude Code, Claude Desktop, Cursor and Codex use Codz on your Mac, from your usage and plan limits to your chats, projects and scripts, through codz mcp.

codz mcp is an MCP server for the other apps on your Mac. Add it to Claude Code, Claude Desktop, Cursor or Codex, and they can read your usage and plan limits, start and follow Codz chats with any agent you have set up, and see your projects, the agents working right now, your development servers and your scripts.

It talks to the Codz that is running, so it can do only what Codz itself does. Every edit and command a chat wants still waits for your approval in Codz.

Add Codz to an app

Open Settings ▸ Connections. Under Apps on this Mac:

Claude Code and Codex: Add… opens Agent integrations with the app’s own command filled in. Nothing runs until you select Run.
Cursor and Claude Desktop: Copy copies the server entry. Paste it into the app’s MCP configuration: ~/.cursor/mcp.json for Cursor, claude_desktop_config.json for Claude Desktop.

From a terminal, with the codz command set up:

claude mcp add -s user codz -- ~/.local/bin/codz mcp

codex mcp add codz -- ~/.local/bin/codz mcp

The entry for Cursor and Claude Desktop names the full path, because those apps do not expand ~:

{
  "mcpServers": {
    "codz": {
      "args": ["mcp"],
      "command": "/Users/you/.local/bin/codz"
    }
  }
}

What other apps can do

Tools	What they do
`get_usage`	Tokens and estimated cost for a day or a range of days, by provider, model or day. The free plan reads the last seven days; older days are Codz Pro.
`get_plan_limits`	How much of Claude’s 5-hour and 7-day windows, Codex’s windows and Cursor’s billing cycle is used, when each resets, and where the current pace leads
`list_chats`, `read_chat`	Your Codz chats, newest first, and a chat’s latest turns
`start_chat`, `send_message`, `wait_for_chat`, `stop_chat`	Start a chat with an agent set up in Codz, message it, wait for its answer, and stop its turn
`list_projects`, `list_agents`, `list_ports`	Your projects, the agents working on this Mac in Codz or not, and your development servers
`list_scripts`, `run_script`, `get_script_run`, `stop_script`	A project’s scripts, run as they would be from the Scripts panel

Costs are estimates at each provider’s API list prices, not what a subscription bills, except where a provider states its own charge.

What stays with you

Approvals and questions. Only you answer them: in Codz, on your phone, or with codz in your own terminal. No app can, and neither can an agent working in a Codz chat.
What a chat may change. A chat an app starts begins in ask mode, which answers without changing files. In agent mode it runs at Reviewed, so every edit and command waits for you. An app can message the chats it started and chats that cannot change anything without asking; a chat you set to edit or run on its own is yours to steer.
Where it works. Apps start chats only in a project’s folder or one that already has chats, never in your home folder, and never on OpenRouter or DeepSeek, which are billed per token through a key Codz holds.
How much. One app starts at most twelve chats an hour, and apps have at most four working at once.
The switch. Turn off Let other apps use Codz and Codz refuses every app at once.

A chat an app starts appears in your sidebar like any other, and its first message says which app sent it.

When Codz is not running

codz mcp needs Codz. The installed app starts its background host when an app first calls a tool. Codz Development must be open first, and a tool call answers with what to open until it is.