Requires Builder plan or above. Your MCP server must support Streamable HTTP transport.
How it works
- You configure your MCP server URL on the tenant
- At chat time, Animam calls
tools/liston your server to discover available tools - Tools are injected into the AI’s context (prefixed
mcp_to avoid collisions) - When the AI decides to use one, Animam calls
tools/callon your server - The result is returned to the AI, which incorporates it in its response
- Tool discovery is cached for 5 minutes per tenant
GET /tenants//mcp-tools
Read current MCP tools configuration. Required scope:settings:read
Request
Response
PUT /tenants//mcp-tools
Configure or update the external MCP server connection. Required scope:settings:write
Request
Response
DELETE /tenants//mcp-tools
Remove MCP tools configuration. Required scope:settings:write
Configuration fields
MCP server requirements
Your server must implement the MCP specification with Streamable HTTP transport:POST /mcp— Handle JSON-RPC requeststools/list— Return available tools with name, description, and input schematools/call— Execute a tool and return the result
Minimal server example (Node.js)
Authentication
IfmcpToolsApiKey is set, Animam sends it as a Bearer token:
Debugging
If tools don’t appear in chat:- Check that
mcpToolsUrlis reachable from the Animam API server - Verify your server responds to
tools/listwith valid tool definitions - Check that
mcpToolsMaxToolsis high enough to include your tools - Tools are cached — wait 5 minutes or restart the chat session
- Verify your plan is Builder or above