Consume Platos via MCP

Point Claude Desktop, Cursor, or any MCP client at Platos to use its tools and meta-tools from a chat that lives outside Platos.

The goal

An MCP client connected to your Platos instance. The client's tool catalogue federates entity tools, Platos skills, trigger meta-tools, and the Platos control plane.

Steps

Mint a PAT.

Settings -> MCP tokens -> "New token". Name it (claude-desktop-pat), pick scope, pick permission scopes (tools:execute, agents:read is a good starter set). Copy the pmt_... string.

Configure your MCP client.

Claude Desktop's ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "platos": {
      "url": "https://platos.example.com/mcp",
      "headers": {
        "Authorization": "Bearer pmt_abc123..."
      }
    }
  }
}

Restart Claude Desktop.

List tools.

In the MCP client, list available tools. You should see entity tools, skill tools, meta-tools, and control-plane tools all in one catalogue.
Scope per-entity (optional).

If you only want one entity's tools, point at the per-entity endpoint instead:
```
https://platos.example.com/mcp/entities/my-entity
```
Branding (PIFSP-24) means the connector shows the entity's own name.

Verify

The client's tool list shows tools from your Platos instance.
A tool call works end-to-end (e.g. agents.list returns your agents).
The "Last used" column on the PAT row in /settings/mcp-tokens updates.

Why the bearer is rejected

Token must start with pmt_. The recent fix (commit adfe32e6b) accepts both PAT and OAuth bearers; older deployments may only accept the OAuth shape.
Token must have the right scopes. A PAT scoped only agents:read cannot execute tools.
Token must be in the right scope (org/project/env). MCP gateway picks the scope from the PAT.

Next steps

Connect an entity (TypeScript) to add your own tools to the federation.
Embed a public agent for the consumer-facing alternative.