
Twelvelabs Mcp Server
io.github.micro-JAYPublished by GitHub account micro-JAYv1.0.1Updated Oct 24, 2026
MCP server for ElevenLabs Conversational AI (not TwelveLabs video) — agents, KB, voices
The publisher's own server: Twelvelabs Mcp Server
Overview
Lets an assistant manage ElevenLabs Conversational AI voice agents, knowledge base documents, conversations, and voices through the ElevenLabs API.
- What you can do
- Provides tools for listing and inspecting agents, reading and updating system prompts, settings, and webhooks, and managing knowledge base documents (list, read, add text or URL, delete). It also lists and filters conversation history, retrieves transcripts and evaluation results, reruns post-call analysis or evaluation, manages conversation tags, and browses available voices.
- When to use it
- Useful when you want an assistant to inspect or edit ElevenLabs voice agents and their prompts, settings, and knowledge base, or to review and tag past conversations without opening the ElevenLabs dashboard.
- Requirements
- Runs locally over stdio; needs Node.js 18 or later and an ElevenLabs API key supplied as the ELEVENLABS_API_KEY environment variable. The MCP client must support stdio and allow configuring environment variables for a local process.
Installation
In SourceWeft
- Open Twelvelabs Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
TwelveLabs MCP Server
This project is not affiliated with TwelveLabs (the video understanding platform). It is an MCP server for the ElevenLabs Conversational AI API — voice agents, knowledge bases, conversations, and TTS. The name "TwelveLabs" is the project codename only.
An enhanced MCP (Model Context Protocol) server that gives any compatible MCP client direct access to the ElevenLabs Conversational AI API -- including capabilities the official ElevenLabs MCP connector doesn't expose.
What this covers
- Agents -- list, get full config (including LLM model + temperature), update prompt/settings, manage webhooks and file uploads
- Knowledge Base -- list, read full content, add text/URL docs, delete docs
- Conversations -- filter and tag history, inspect transcripts, and rerun post-call analysis/evaluations
- Voices -- list and search available voices
Prerequisites
- Node.js >= 18
- ElevenLabs API key -- get one at elevenlabs.io
Quick Start
Option A: npx (no clone needed)
Option B: Clone and build
Connect an MCP client
Add an equivalent server entry to your MCP client's configuration. The config file location and surrounding syntax vary by client; this is the standard stdio server definition:
Restart or reconnect your MCP client. You should see twelvelabs in its
available tools list.
Use it
Ask your MCP-enabled assistant to use the tools, for example:
"List my agents" "Get the full config for agent_1001kjbh14xce5kbreh55ydf4rae" "Show me the last 10 conversations for that agent" "Get the transcript and analysis for conversation_xyz"
Compatibility
This server works with MCP clients that support the stdio transport and let you configure environment variables for a local server process. Clients that only support remote HTTP MCP servers need a compatible stdio bridge or proxy.
Tool Reference
Agent Tools
Knowledge Base Tools
Conversation Tools
Voice Tools
Security
- Input validation -- all tool parameters are validated with Zod schemas before reaching the API
- HTTPS enforcement -- webhook URLs are validated to use HTTPS only
- Path traversal protection -- document and agent IDs are sanitized to prevent path traversal
- Error sanitization -- internal errors are caught and returned as safe MCP error responses; raw stack traces are never exposed to the client
Development
Contributing
- Fork the repository
- Create a feature branch (
git checkout -b feat/my-feature) - Commit your changes (
git commit -m 'feat: add my feature') - Push to the branch (
git push origin feat/my-feature) - Open a Pull Request
License
MIT -- see LICENSE for details.
Architecture Note
All tools share a single Axios client instance (src/client.ts) initialised from
ELEVENLABS_API_KEY at startup. Tool implementations live in src/tools/ -- one
file per domain -- and are registered onto the McpServer in src/index.ts. The
server communicates over stdio transport (stdin/stdout), which is why all debug
logging uses console.error (stderr), not console.log.
Source: README.md at commit f478ecb
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 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