MCP server · Catzoid familycoming soon

MCatzP.

em-catz-pee

The MCP with the cats inside.

One MCP server for the whole family. Your AI assistant will reach DevCatz, DBCatz, DialCatz and DoCatz through a single connection — and you hold the keys.

How it will workWatch on GitHub

Apache-2.0runs on your Macany MCP client

Every cat, one connection

Ask your assistant. The right cat answers.

Each cat brings its own tools, named after it. Your assistant picks the cat; the cat does the work under its own rules.

DevCatz

devcatz_*

“Why does shop.localhost return 500?”

  • List sites and services, with their status
  • Start, stop or restart a site
  • Read its logs and the errors in them
  • Name the .env lines a site still needs

DBCatz

dbcatz_*

“Which customers paid twice this month?”

  • List the connections you share
  • Read databases, tables and columns
  • Run read-only queries, with a row limit
  • Never write — not even on a dev database

DialCatz

dialcatz_*

“Send the login request and check the token.”

  • List workspaces, collections and environments
  • Send a saved request
  • Run a collection on the environment you pick
  • Read the last responses, secrets masked

DoCatzsoon

docatz_*

“Why does the api container keep restarting?”

  • List containers and images
  • Read a container’s logs
  • Start, stop or restart a service

How it will work

One line, then ask.

Planned setup — the details may still change before the first release.

  1. 01

    Bring it home

    With Homebrew, or straight from npm — nothing to configure yet.

    $ brew install catzoidhub/catz/mcatzp
    $ npx mcatzp
  2. 02

    Introduce it to your assistant

    One command in Claude Code, or one entry in any client's MCP settings.

    $ claude mcp add mcatzp -- npx mcatzp
    {
  "mcpServers": {
    "mcatzp": { "command": "npx", "args": ["mcatzp"] }
  }
}
  3. 03

    Open the cat flap

    In each cat: Settings → AI → MCatzP. Switch it on and pick exactly what your assistant may see. Then just ask.

You hold the keys

One connection.
Every cat. Your rules.

MCatzP never reaches into a cat on its own: each cat answers for itself, with the same production guard, read-only switch and confirmations you already know from the app.

  • Off until you switch it onPer cat, in Settings → AI → MCatzP. A cat that is not installed, or has it off, simply has no tools.
  • Only what you shareYou pick the sites, the database connections, the workspaces and the containers your assistant may see.
  • Every change asks in the appStarting a site or sending a request opens a confirmation in the cat itself — never just a line in the chat.
  • Secrets stay putPasswords, tokens, .env values and Authorization headers are masked unless you share one on purpose.
  • Local onlyMCatzP runs on your Mac next to the cats. It is never opened to the internet.
  • A log of every callEach cat keeps an activity log: what was asked, by which assistant, allowed or refused.

Works with

Any assistant that speaks MCP.

MCP is an open protocol, so MCatzP does not care which model is on the other end — only that its app can call tools.

Apps

Claude DesktopClaude CodeCursorVS CodeGemini CLICodex CLIClineRoo CodeOpenCodeZed

Models

ClaudeGeminiGPTGLMDeepSeekQwenlocal models via Ollama

One honest limit: MCatzP lives on your Mac, so assistants that only run in a browser tab (and reach out from their own servers) cannot see it — and it will never be opened to the internet for them. Desktop apps and command-line tools can.

Coming after the first release

Meet the cats first.

MCatzP follows right after the cats ship on Apple silicon, Intel and Windows. Until then, adopt one — they already know each other.

Download the catsSee the roadmap