
Anima
io.github.anima-labs-aiPublished by GitHub account anima-labs-aiv1.0.1Updated Oct 24, 2026
Give your AI agent an identity it owns: email inbox, US phone number, SMS, voice, and a vault.
Overview
Hosted MCP gateway that gives an AI agent its own identity: email inbox, US phone number, SMS, voice, and an encrypted credential vault.
- What you can do
- Manage agent identities: create, get, list, update and delete agents
- Handle email: create mailboxes, send, reply, forward, read threads, drafts and attachments, use custom domains
- Handle phone: provision numbers, work with SMS threads, place voice calls and read transcripts and recordings
- Use the encrypted vault: store, search and update credentials, generate TOTP, request credentials, manage OAuth connections and Connect Links
- Review account and usage overviews and manage webhooks
- Connect a browser extension in headless or Puppeteer mode
- When to use it
- Use it when you want an assistant to act as a real correspondent and caller — sending and receiving email from its own mailbox, texting and calling from a provisioned number — and to hold credentials it can use server-side without exposing them in chat.
- Requirements
- Remote streamable HTTP endpoint at mcp.useanima.sh; no local runtime needed. Authentication uses a bearer token in the Authorization header (an ak_ or mk_ key). A local stdio variant exists as a separate package for those who prefer it. An Anima account is implied by the key.
Installation
In SourceWeft
- Open Anima in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.anima-labs-ai%2Fanima/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"anima": {
"type": "http",
"url": "https://mcp.useanima.sh/mcp"
}
}
}README
@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)
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:
History
Replaces five separate packages (mcp-agent, mcp-email, mcp-phone, mcp-platform, mcp-vault) and the mcp-core shared library.
Source: README.md at commit 994abe8
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts