Open app
Moonborn — Developers

MCP server integration

Connect Claude / Cursor / agent frameworks to Moonborn via the Model Context Protocol server. Personas appear as resources, chat as a tool.

Moonborn exposes a Model Context Protocol (MCP) server at https://api.moonborn.co/v1/mcp. Any MCP-compatible client — Claude for VS Code, Cursor, JetBrains, an agent framework that speaks the protocol — can list your workspace's personas as resources and invoke chat sessions as a tool.

1. Configure your MCP client

Most clients accept an MCP server entry in their settings. The shape varies per client; the connection details don't:

{
  "mcpServers": {
    "moonborn": {
      "transport": "https",
      "url": "https://api.moonborn.co/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${MOONBORN_API_KEY}"
      }
    }
  }
}

For Claude for VS Code, add this to ~/.config/claude/mcp.json (macOS) or the equivalent on your OS. For Cursor, the settings panel has an "MCP Servers" section.

2. List resources

Once connected, the client can enumerate Moonborn's resources:

mcp> list resources
moonborn:personas/persona_01H...  — "Mert Aksoy"
moonborn:personas/persona_02H...  — "Leyla Demir"
moonborn:personas/persona_03H...  — "Brand voice — canonical"

Each resource exposes:

  • The persona's full four-layer document (read-only from MCP).
  • The voice fingerprint ID.
  • The current audit verdict + score.

3. Read a resource

mcp> read moonborn:personas/persona_01H...

The client receives the full persona document as MCP resource content. Claude can now answer questions like "what's this persona's growth arc?" by reading the resource directly.

4. Invoke the chat tool

The MCP server exposes a chat tool that opens a session and sends a message in one call:

mcp> call moonborn.chat
  persona: moonborn:personas/persona_01H...
  message: "Tell me about your last quarter."

The tool returns the reply, the drift envelope, and the session ID (useful for continuation across turns).

5. Limits

The MCP server is scoped to read-only resource access + the chat tool. You cannot:

  • Create or delete personas via MCP — use the REST API.
  • Modify the workspace config from MCP.
  • Access audit logs or webhook deliveries from MCP.

For full read/write, hit the REST surface directly. MCP is the narrow, IDE-friendly entry point.

6. Authentication scopes

The bearer token must have at minimum:

  • read:personas — to list and read resources.
  • write:chat — to invoke the chat tool.

Issue a scoped API key in Settings → API keys → New key if you want to give an MCP client a least-privilege credential.

Tier

Team and up.

Honest scope

The MCP server serves personas to MCP clients. It is not a general agent host, not a full LLM router, not an alternative to the chat completions endpoint. It's a narrow protocol bridge for IDE + agent framework users.

Next