io.github.anima-labs-ai/anima
Give your AI agent an identity it owns: email inbox, US phone number, SMS, voice, and a vault.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http anima 'https://mcp.useanima.sh/mcp'
{
"mcpServers": {
"anima": {
"type": "http",
"url": "https://mcp.useanima.sh/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
@anima-labs/mcp-server
The hosted MCP server behind https://mcp.useanima.sh — the recommended way to connect AI assistants to Anima. It exposes the full tool surface (66 tools today) over streamable HTTP with Authorization: Bearer <ak_… or mk_…>.
This package is deliberately not published to npm: it is the deployed gateway. For a local/stdio server use @anima-labs/mcp (published, 53 core tools) — same platform, same auth. Client setup for both lives in the MCP docs, or run anima setup-mcp.
Endpoints
One gateway, scoped mounts. /mcp carries everything; the per-domain mounts serve tailored connections with a smaller tool count:
/mcp— all tools (recommended)/agent— agent lifecycle (create/get/list/update/delete)/email— Anima agent mailboxes: inbox create/get/list/update/delete, send/reply/forward, threads, drafts, attachments, custom domains (agents.useanima.shaddresses or your own domain — no Gmail/SMTP relay involved)/phone— phone number provisioning, SMS threads, voice calls + transcripts/recordings (Telnyx-backed)/platform— account/usage overviews and webhook management/vault— encrypted credential vault: CRUD, search, TOTP, server-side use, credential requests, OAuth connections, Connect Links/extension— browser extension connect (headless / Puppeteer)
Run locally (development)
bun run src/index.ts
Environment: ANIMA_API_URL (defaults to a local dev API at http://127.0.0.1:3100; the production deployment sets it to the live API), MCP_BASE_URL, PORT.
Deploy production (mcp.useanima.sh)
Preferred path is GitHub Actions: run Deploy MCP Server (.github/workflows/deploy.yml) via workflow_dispatch.
Required repository secrets (for Workload Identity Federation / OIDC):
GCP_WORKLOAD_IDENTITY_PROVIDER(format:projects/<number>/locations/global/workloadIdentityPools/<pool>/providers/<provider>)GCP_SERVICE_ACCOUNT_EMAIL(deployer service account inanima-labs)
Workflow behavior:
- Builds and pushes
us-central1-docker.pkg.dev/anima-labs/anima/mcp-server:<tag> - Deploys Cloud Run service
mcp-serverinus-central1 - Prints
GET /healthresponse so you can confirmstartedAtchanged
Manual fallback (same image/deploy settings) remains:
./deploy.sh <tag>
History
Replaces five separate packages (mcp-agent, mcp-email, mcp-phone, mcp-platform, mcp-vault) and the mcp-core shared library.
Frequently asked questions
What is io.github.anima-labs-ai/anima?
Give your AI agent an identity it owns: email inbox, US phone number, SMS, voice, and a vault.
How do I install io.github.anima-labs-ai/anima?
It runs as a remote server. In Claude Code: claude mcp add --transport http anima 'https://mcp.useanima.sh/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.anima-labs-ai/anima need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.anima-labs-ai/anima open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.anima-labs-ai/anima?
It is published by anima-labs-ai. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.