Can I use ElevenLabs as a CLI?

Yes. KosmoKrator exposes a ElevenLabs CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose ElevenLabs through MCP?

Yes. The KosmoKrator MCP gateway can expose selected ElevenLabs tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are ElevenLabs credentials stored?

ElevenLabs credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for ElevenLabs MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

ElevenLabs MCP Gateway for AI Agents

Expose ElevenLabs tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

8 functions 5 read 3 write API key auth

Submit ElevenLabs feedback View package source

ElevenLabs MCP Gateway

Expose ElevenLabs to MCP clients with `kosmokrator mcp:serve --integration=elevenlabs`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.

curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

kosmokrator mcp:gateway:install --integration=elevenlabs --write=deny --json

{
  "mcpServers": {
    "kosmokrator-elevenlabs": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=elevenlabs",
        "--write=deny"
      ]
    }
  }
}

Serve Manually

kosmokrator mcp:serve --integration=elevenlabs --write=deny

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP tool	Source function	Type
`integration__elevenlabs__elevenlabs_text_to_speech`	`elevenlabs.elevenlabs_text_to_speech`	Write `write`
`integration__elevenlabs__elevenlabs_list_voices`	`elevenlabs.elevenlabs_list_voices`	Read `read`
`integration__elevenlabs__elevenlabs_get_voice`	`elevenlabs.elevenlabs_get_voice`	Read `read`
`integration__elevenlabs__elevenlabs_create_voice`	`elevenlabs.elevenlabs_create_voice`	Write `write`
`integration__elevenlabs__elevenlabs_delete_voice`	`elevenlabs.elevenlabs_delete_voice`	Write `write`
`integration__elevenlabs__elevenlabs_get_models`	`elevenlabs.elevenlabs_get_models`	Read `read`
`integration__elevenlabs__elevenlabs_get_history`	`elevenlabs.elevenlabs_get_history`	Read `read`
`integration__elevenlabs__elevenlabs_get_current_user`	`elevenlabs.elevenlabs_get_current_user`	Read `read`

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.