Skip to main content
Anam’s MCP server lets your AI app build and manage personas (real-time AI avatars that talk with people over video), review their conversations and write code to add them to your app. Anam hosts it; there’s nothing to install.
Server URL
You sign in with your Anam account and choose one organization. The connection reaches only that organization.

Connect an app

The first time, your app opens Anam in a browser. Sign in or sign up, choose the organization and choose the access to give it (see Access and safety).
These steps work on claude.ai and in the Claude desktop app.
1

Add a custom connector

In Claude, open Settings, then Connectors, and choose Add custom connector.
2

Paste the server URL

Name it Anam, paste https://lab.anam.ai/mcp and add it.
3

Sign in

Choose Connect and sign in to Anam.
On Team and Enterprise plans, an owner adds the connector in the organization’s settings first.
To check the connection, ask your app “Which Anam organization am I connected to?” It runs anam_connection_info, which returns the organization, the access you chose and the app. If it can’t connect, see Troubleshooting.

Agents without a browser: API keys

Agents that run without a browser, such as CI jobs, can send an Anam API key as Authorization: Bearer <key> instead of signing in. They act with the key’s permissions and don’t appear under Connected apps on the AI apps page. Create and revoke keys on the API keys page. Keep the key in an ANAM_API_KEY environment variable and have the client read it from there, so it never sits in a config file:

Access and safety

When you connect, you choose one organization and, if the app asks for both, its access: An app Anam can’t verify is marked Unverified on the sign-in page and starts at Read only; choose Full access only if you trust it.
  • Confirmations. Before the app deletes something, starts paid work (creating an avatar or avatar video, cloning a voice, sending a persona to a meeting), generates speech (importing a voice or changing its model) or adds a knowledge document (documents count towards your monthly upload allowance), Anam asks you to confirm in the app, and the action runs only if you approve. Apps that can’t show Anam’s question (MCP elicitation) are instead told to ask you first; Anam can’t enforce that, so it depends on the app.
  • Same rules as the API. Every tool runs Anam’s public API with your connection’s own key, so the same permissions, organization boundaries, plan limits, rate limits and audit log apply.
  • Secrets stay hidden. Results never show stored API keys, and webhook headers, tokens and similar values show as ••••. LLM provider keys you add are stored encrypted and never returned.
  • Untrusted content. The app is told to treat what tools return (transcripts, documents, web pages) as data, not instructions.
  • Docs searches. anam_docs_search and anam_docs_read send the search text or read command to Anam’s public docs, hosted by Mintlify, with no account details. Send documentation terms, not customer content or secrets.

Tools

  • Personas: create one from a short brief or from Anam’s defaults, change its prompt, avatar, voice and language model, and get a share link to talk to it.
  • Avatars, voices and LLMs: browse what your organization can use, create an avatar from an image, import a voice from a provider or clone one from a recording, and add your own LLM.
  • Knowledge: make folders, add documents from text or web pages, search them and attach them to personas.
  • Sessions: find conversations by date, persona or what was said, read transcripts, and see reply speed and failures.
  • Meetings and video: send a persona to a Google Meet, Zoom or Microsoft Teams call, and generate avatar videos.
  • Building: starter code for Next.js, Express or FastAPI, integration guides and search over these docs.
Conversations with a persona happen in a browser or your own app, not in the chat. Your Anam plan’s limits and charges apply, as in Anam Lab. Most tools run one Anam API operation; the workflow tools under Start here do several steps at once. A read-only connection gets only the read tools. Apps installed from a directory listing get a smaller set made for that platform (see Directory tool sets below); everywhere else, use /mcp, which has every tool.
  • anam_connection_info: the connected organization, access and app.
  • anam_usage_get: plan, minutes used and left, live sessions against the limit, and knowledge uploads this month.
  • anam_options: avatars, voices and LLMs in one list, with Anam’s recommended picks.
  • anam_quickstart: a working persona and a share link in one call, from Anam’s defaults or a template (sales, support, receptionist, tutor, interviewer).
  • anam_persona_from_brief: a persona with a written system prompt and greeting from a description.
  • anam_avatar_list, anam_avatar_get, anam_avatar_create (from an image URL), anam_avatar_update, anam_avatar_delete
  • anam_avatar_video_create, anam_avatar_video_list, anam_avatar_video_get, anam_avatar_video_cancel, anam_avatar_video_retry, anam_avatar_video_delete
  • anam_voice_list, anam_voice_get, anam_voice_import, anam_voice_update, anam_voice_delete
  • anam_voice_clone: a new voice cloned from a recording at a public URL (10 to 15 seconds of one person speaking, up to 10 MB). Only clone the voice of someone who has consented.
  • anam_llm_list, anam_llm_get, anam_llm_create, anam_llm_update, anam_llm_delete: your own LLM endpoints.
  • anam_pronunciation_dictionary_list, anam_pronunciation_dictionary_get, anam_pronunciation_dictionary_create, anam_pronunciation_dictionary_import, anam_pronunciation_dictionary_update, anam_pronunciation_dictionary_delete
  • anam_knowledge_folder_list, anam_knowledge_folder_get, anam_knowledge_folder_create, anam_knowledge_folder_update, anam_knowledge_folder_delete, anam_knowledge_folder_search
  • anam_knowledge_document_create_from_text, anam_knowledge_document_create_from_url: add a document; it becomes searchable once processed.
  • anam_knowledge_document_list, anam_knowledge_document_get, anam_knowledge_document_update, anam_knowledge_document_delete, anam_knowledge_document_download
  • anam_persona_knowledge_add, anam_persona_knowledge_remove: attach or detach knowledge folders, as the Build page does.
  • anam_tool_list, anam_tool_get, anam_tool_create, anam_tool_update, anam_tool_delete: webhooks and client tools a persona can call.
  • anam_session_search: find sessions by date, persona or what was said, or page through one transcript.
  • anam_session_insights: how one call, or every call in a period, went: reply speed, interruptions, errors and failed tool calls.
  • anam_session_list, anam_session_get, anam_session_transcript_get, anam_session_analytics_get, anam_session_stats, anam_session_recording_get, anam_session_concurrency_get
  • anam_session_stop: end a live session. anam_session_delete: delete a session, its recording or its report.
  • anam_session_token_create: a short-lived session token for trying an app locally. It starts at most 10 sessions unless you ask for more (up to 100).
  • anam_meeting_invite_create, anam_meeting_invite_list, anam_meeting_invite_get, anam_meeting_invite_cancel: send a persona to a Google Meet, Zoom or Microsoft Teams meeting.
  • anam_integration_guide: the session-token pattern and a docs excerpt for JavaScript, React, LiveKit, Python, ElevenLabs or the widget.
  • anam_scaffold: starter files for Next.js, Express or FastAPI, with your persona’s ID filled in and the API key kept on the server.
  • anam_docs_search, anam_docs_read: search and read these docs.
Each directory listing connects to its own path, with the tools that platform’s rules allow. A token issued for one path doesn’t work on another.
  • /mcp/claude: the Claude connectors directory
  • /mcp/chatgpt: the ChatGPT plugin directory
  • /mcp/copilot: Microsoft 365 Copilot
  • /mcp/gemini: Google’s Gemini
  • /mcp/agentforce: Salesforce Agentforce
  • /mcp/muse: Meta Muse

Disconnect or turn off AI apps

  • AI apps in Anam Lab lists the organization’s connected apps, with their access, who connected them and when they were last used. Disconnecting stops an app at once; it has to sign in again to come back. Members disconnect their own apps, and owners and admins anyone’s.
  • Owners and admins can turn off Allow AI apps on the same page. That disconnects every member’s apps and the organization’s agent clients, and refuses MCP requests with its API keys (the keys keep working for the rest of the API). Nobody can connect an app until it’s turned on again. Organizations that require SSO start with AI apps off.
  • Resetting your password or signing out everywhere also disconnects your apps. For an agent that uses an API key, revoke the key.

Docs-only MCP server

To let an assistant search and read these docs without connecting an Anam account, add the docs MCP server instead. It needs no sign-in and can’t reach your account.
Docs server URL
Claude Code
The account server above already includes docs search (anam_docs_search and anam_docs_read), so you don’t need both.

Troubleshooting

Help

Last modified on November 6, 2026