Platica MCP Server
Platica's MCP server (Model Context Protocol) exposes every REST API endpoint as a tool that can be invoked from any compatible MCP client: Cursor, Claude Code, Claude Desktop (via mcp-remote), VS Code Copilot, your own agents, etc.
With a single URL and your existing API Key, you give your LLMs secure access to conversations, customers, agents, campaigns, templates, webhooks, tags, and custom fields.
Server URL
https://api.platica.mx/mcp- Method:
POST(JSON-RPC 2.0 over Streamable HTTP) - Authentication:
Authorization: Bearer pl_key_...(the same API Key you use for the REST API) - Mode: stateless + JSON (no persistent sessions or SSE required)
- Spec: Streamable HTTP
2025-11-25
What's included?
41 ready-to-use tools — One for every production endpoint of the Platica REST API.
Same authentication — Reuse your current API Keys. Whatever a REST endpoint can do, its MCP tool can do in exactly the same way.
No extra server — Connect your client directly to
api.platica.mx/mcp. You don't need to install anything locally.Auto-generated schemas — Every tool publishes its
inputSchema(JSON Schema) so the LLM knows exactly which arguments to send.
Next steps
| Section | Description |
|---|---|
| Setup | Connection snippets for Cursor, Claude Code, Claude Desktop, and other clients |
| Authentication | How to generate and use your API Key with the MCP server |
| Tools — Introduction | Naming conventions, annotations, and full catalog |
| Errors | How REST errors map to MCP responses |
If you're already authenticated against the REST API, the MCP integration requires no additional steps on the server side — just configure your client.