Cato MCP CMA MCP Server

This repository provides a local mcp-server for Cato Network's public GraphQL API

Local serverstdio

What is the Cato MCP CMA MCP server?

Cato MCP CMA MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. This repository provides a local mcp-server for Cato Network's public GraphQL API.

What you get

A Model Context Protocol (MCP) server implementation that integrates with Cato CMA Public API.

This server implements the Model Context Protocol to allow AI assistants to interact with Cato's GraphQL API. It provides tools that enable AI models to query and retrieve information from Cato systems in a standardized way.

What the assistant can call

Once Cato MCP CMA is connected, these are the calls the assistant has available:

  • Category — Tool
  • Sites — sites_by_location

Configuration and credentials

You will need 4 environment variables: CATO_API_HOST, CATO_ACCOUNT_ID, CATO_API_KEY, CATO_LOG_LEVEL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cato MCP CMA's toolset — Category, Sites — is a fair guide to whether it matches your workflow. It is maintained by catonetworks; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the cato mcp cma mcp server does with a few real requests.

Available tools

ToolWhat it does
CategoryTool
Sitessites_by_location

How to install the Cato MCP CMA MCP server

{
  "mcpServers": {
    "cato": {
      "command": "docker",
      "args": [
          "run",
          "--rm",
          "--pull",
          "always",
          "-i",
          "-e", "CATO_API_HOST=<your Cato API Host>",
          "-e", "CATO_ACCOUNT_ID=<your Cato Account ID>",
          "-e", "CATO_API_KEY=<your Cato API Key>",
          "ghcr.io/catonetworks/cato-mcp-server:latest"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CATO_API_HOSTEndpoint or connection string the server talks to.Optional
CATO_ACCOUNT_IDConfiguration value read at startup.Optional
CATO_API_KEYCredential the server authenticates with.Yes
CATO_LOG_LEVELConfiguration value read at startup.Optional

Example prompts to try

  • Use Cato MCP CMA to Category.
  • Use Cato MCP CMA to Sites.

Frequently asked questions

Tested with Cursor and Claude Desktop (non-free tier) using the Claude Sonnet 4 model.