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, VS Code Copilot, your own agents, etc.
With a single URL you give your LLMs secure access to conversations, customers, agents, campaigns, templates, webhooks, tags, and custom fields. You authenticate with OAuth (the same account as the dashboard) or with the API Key you already use for REST.
Server URL
https://api.platica.mx/mcp- Method:
POST(JSON-RPC 2.0 over Streamable HTTP) - Authentication: OAuth 2.1 (recommended) or
Authorization: Bearer pl_key_... - Mode: stateless + JSON (no persistent sessions or SSE required)
- Spec: Streamable HTTP
2025-11-25
What's included?
Ready-to-use tools — One for every production endpoint of the Platica REST API.
The same API, two doors — OAuth connects you with your user and your role. An API Key covers the whole workspace, same as REST. Whatever an 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, VS Code, and other clients |
| Authentication | OAuth 2.1 (sign-in + workspaces) and API Key |
| Tools — Introduction | Naming conventions, annotations, and full catalog |
| Workspaces | list_workspaces: the first tool after connecting with OAuth |
| Errors | How REST errors map to MCP responses |
If your client speaks OAuth, paste https://api.platica.mx/mcp and authorize. You don't need to generate an API Key.