@animam/mcp

Stdio bridge to the remote Animam MCP server (mcp.animam.ai). Lets any local MCP client (Claude Desktop, Cursor, Claude Code…) manage an Animam chatbot tenant — persona, branding, widget UX, knowledge base, segments, bots — with the same tools as the dashboard.

It is a thin proxy: it forwards tools/list and tools/call to the remote server over SSE, authenticated by your API token. No business logic, no database access.

Usage

Add to your MCP client config (e.g. ~/.claude/settings.json):

{
  "mcpServers": {
    "animam": {
      "command": "npx",
      "args": ["-y", "@animam/mcp"],
      "env": {
        "ANIMAM_API_TOKEN": "ak_your_token"
      }
    }
  }
}

Create the token in the Animam dashboard → Settings → API tokens. Scopes gate which tools the token can call (settings:write for tenant config, corpus:write for the knowledge base, * for everything).

Environment

| Variable | Required | Description | |----------|----------|-------------| | ANIMAM_API_TOKEN | Yes | Animam API token (ak_…) or OAuth access token | | ANIMAM_MCP_URL | No | Remote MCP base URL (default https://mcp.animam.ai) |

Equivalent without this package

npx -y mcp-remote https://mcp.animam.ai/mcp/sse --header "Authorization: Bearer ak_your_token"

@animam/mcp just bakes in the endpoint. See the docs.