clix-so-mcp.yml

Clix has two MCP surfaces and neither one executes Clix operations — both retrieve documentation. (1) The provider-built "Clix MCP Server" is a stdio npm package, @clix-so/clix-mcp-server 0.1.4, run with `npx -y @clix-so/clix-mcp-server@latest`; its two tools, search_docs and search_sdk, do semantic search over the docs llms.txt index and over the four SDK source repos (read from src/tools/index.ts and src/tools/descriptions.ts in the repo — the server was not run). (2) A remote Streamable HTTP endpoint at https://docs.clix.so/mcp is served by Mintlify for the docs site: initialize and tools/list answer anonymously (protocol 2025-06-18, serverInfo "Clix Documentation" 1.0.0) with three platform tools — search_clix_documentation, query_docs_filesystem_clix_documentation and submit_feedback — and one resource, mintlify://skills/clix. The operational agent surface (create users, track events, send pushes, trigger campaigns) is NOT MCP; it is the A2A agent at https://api.clix.so/a2a (a2a/clix-so-a2a.yml), and the docs say so explicitly ("Use Clix MCP Server when your assistant needs context. Use A2A when your agent needs to execute work inside Clix.").

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.