Cato MCP CMA

Created By
catonetworksa year ago
This repository provides a local mcp-server for Cato Network's public GraphQL API
Overview

what is Cato MCP CMA?

Cato MCP CMA is a Model Context Protocol (MCP) server implementation that allows AI assistants to interact with Cato Network's public GraphQL API, enabling standardized queries and information retrieval from Cato systems.

how to use Cato MCP CMA?

To use Cato MCP CMA, configure the server with your Cato API credentials and run it as a Docker container. You can integrate it with compatible MCP clients like Cursor and Claude Desktop.

key features of Cato MCP CMA?

  • Implements Model Context Protocol for AI integration
  • Compatible with popular MCP clients
  • Provides tools for querying Cato's GraphQL API
  • Docker image available for easy deployment

use cases of Cato MCP CMA?

  1. Enabling AI assistants to access Cato Network data.
  2. Integrating with applications that require real-time data from Cato systems.
  3. Facilitating standardized communication between AI models and Cato's API.

FAQ from Cato MCP CMA?

  • What is required to run Cato MCP CMA?

You need a Cato account, API key, and Docker installed to run the server.

  • Is Cato MCP CMA free to use?

The server is free to use, but you may need a subscription for certain Cato services.

  • Can I customize the server configuration?

Yes, you can customize the server configuration by modifying the environment variables and Docker run commands.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
catonetworks
Star
4
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago