Skip to main content
Glama

Movoice AI MCP Server

npm version License: MIT MCP

Create and manage voice AI agents directly from Claude Desktop or Cursor using natural language — no dashboard required.

"Create a customer support agent for my e-commerce store. Use a friendly female voice and make it handle order status and returns."

That's it. The agent is live and ready to take calls.


What you can do

  • Create a voice AI agent by describing it in plain English

  • List all your agents

  • Update agent prompts, voices, or settings

  • Delete agents

  • View call logs and transcripts


Related MCP server: Bolna MCP Server

Quickstart

Option 1 — npx (no install needed)

{
  "mcpServers": {
    "movoice": {
      "command": "npx",
      "args": ["-y", "@movoice/mcp"],
      "env": {
        "MOVOICE_API_KEY": "mv_live_your_key_here"
      }
    }
  }
}

Option 2 — Install globally

npm install -g @movoice/mcp
{
  "mcpServers": {
    "movoice": {
      "command": "movoice-mcp",
      "env": {
        "MOVOICE_API_KEY": "mv_live_your_key_here"
      }
    }
  }
}

Setup

Step 1 — Get your API key

Go to app.movoice.ai/admin/account → API Keys → Generate Key

Your key looks like: mv_live_xxxxxxxxxxxxxxxx

Step 2 — Add to your client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "movoice": {
      "command": "npx",
      "args": ["-y", "@movoice/mcp"],
      "env": {
        "MOVOICE_API_KEY": "mv_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop.

Cursor

Go to Cursor Settings → MCP → Add Server:

{
  "movoice": {
    "command": "npx",
    "args": ["-y", "@movoice/mcp"],
    "env": {
      "MOVOICE_API_KEY": "mv_live_your_key_here"
    }
  }
}

VS Code (with MCP extension)

Add to .vscode/mcp.json:

{
  "servers": {
    "movoice": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@movoice/mcp"],
      "env": {
        "MOVOICE_API_KEY": "mv_live_your_key_here"
      }
    }
  }
}

Example prompts

Once connected, just talk naturally:

"Create a customer support agent for my e-commerce store called ShopBot. It should handle order status, returns, and general questions. Use a friendly female voice."

"Show me all my agents"

"Update the ShopBot's welcome message to say 'Hi! I'm ShopBot, your shopping assistant. How can I help?'"

"Create a sales agent for an insurance company that qualifies leads and books appointments. Make it speak Hindi."

"Show me the last 10 calls and summarise what customers were asking about"

"Delete the test agent"


Available tools

Tool

Description

list_agents

List all your voice agents

create_agent

Create a new voice agent

get_agent

Get details of a specific agent

update_agent

Update agent settings

delete_agent

Delete an agent

list_calls

View recent call logs

get_call

Get full call details + transcript

create_agent parameters

Parameter

Type

Required

Description

name

string

✅

Agent name (e.g. "Sales Bot")

prompt

string

✅

System prompt — personality, knowledge, behavior

welcomeMessage

string

✅

First thing the agent says when a call connects

llmProvider

string

openai / anthropic / groq (default: openai)

llmModel

string

e.g. gpt-4o-mini, claude-opus-4-6 (default: gpt-4o-mini)

ttsProvider

string

elevenlabs / openai / deepgram / sarvam

ttsVoice

string

Voice ID or name (default: rachel)

asrProvider

string

deepgram / sarvam (default: deepgram)

language

string

Language code e.g. en-US, hi-IN (default: en-US)

webhookUrl

string

Webhook URL to receive call events


Environment variables

Variable

Required

Description

MOVOICE_API_KEY

✅

Your Movoice API key (mv_live_...)

MOVOICE_API_URL

Override API base URL (default: https://app.movoice.ai)


Build from source

git clone https://github.com/Movoiceai/movoice-mcp.git
cd movoice-mcp
npm install
npm run build

Then point your MCP client to dist/index.js:

{
  "mcpServers": {
    "movoice": {
      "command": "node",
      "args": ["/path/to/movoice-mcp/dist/index.js"],
      "env": {
        "MOVOICE_API_KEY": "mv_live_your_key_here"
      }
    }
  }
}


License

MIT © Movoice AI

Available Tools

7 tools
create_agentA

Create a new voice AI agent on Movoice AI. The agent will be ready to take calls immediately.

Inputs: name (required), prompt (required), welcomeMessage (required), language, +6 more.

delete_agentA

Permanently delete a voice AI agent.

Inputs: id (required).

get_agentA

Get details of a specific voice AI agent by its ID.

Inputs: id (required).

get_callA

Get full details of a specific call including transcript and AI analysis.

Inputs: id (required).

list_agentsA

List all voice AI agents in your Movoice AI account.

Inputs: page, per_page.

list_callsA

List recent call logs for your account. Includes duration, sentiment, and transcript availability.

Inputs: page, per_page.

update_agentA

Update an existing voice AI agent. Only provide fields you want to change.

Inputs: id (required), name, prompt, isActive, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: five tools handle agent lifecycle (list/get/create/update/delete), and two handle call logs (list/get). There is no overlap or ambiguity between the tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as list_agents, create_agent, delete_agent, and list_calls. This makes the API predictable and easy for an agent to navigate.

    Tool Count5/5

    Seven tools is a well-scoped set for a voice AI agent management server. Each tool covers a meaningful operation without unnecessary redundancy or bloat.

    Completeness5/5

    The tool surface provides full CRUD coverage for agents and read-only access to call logs, which is exactly what the domain requires. There are no obvious missing operations that would cause agent workflows to fail.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers