MCP server

Mini Agency exposes an HTTP MCP server so trusted clients can inspect and edit a site through the same mutation pipeline as the app.

Endpoint

Use the app origin MCP route:

https://app.miniagency.ai/api/mcp

A GET request is a health and discovery probe. It returns transport information and tool names. MCP clients should use POST JSON-RPC 2.0 requests for initialize, tools/list, and tools/call.

Authentication

The server accepts three auth paths:

• Browser session cookie for signed-in app users.
• Personal MCP token in the Authorization header.
• Platform-admin token for internal admin-only tools.

Personal tokens are created from the app account API keys surface. Tokens start with miniagency_mcp_ and are stored hashed server-side. The plaintext token is shown once. Copy it immediately and store it in your MCP client secret store.

Minimal request shape

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Send it with:

Authorization: Bearer miniagency_mcp_...
Content-Type: application/json

Tool calls

Tool calls use the standard tools/call method:

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "get_basic_info",
    "arguments": {
      "_site": "workspace-slug/site-slug"
    }
  }
}

The _site argument is the safest way to pin the target when a client might operate across multiple sites.

Related docs

• Active-site rule
• Core tools
• Mutations