Voximplant MCP server

voximplant-mcp

An MCP server for Voximplant cloud telephony: call history, call recordings, SMS, ACD and SmartQueue queues, VoxEngine scenarios

MCP serverRussian stack

theyahia/voximplant-mcpAuthor:theYahia

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/voximplant-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio --env 'VOXIMPLANT_ACCOUNT_ID=<VOXIMPLANT_ACCOUNT_ID value>' --env 'VOXIMPLANT_API_KEY=<your VOXIMPLANT_API_KEY>' voximplant -- npx -y @theyahia/voximplant-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "voximplant": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "voximplant": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"voximplant","type":"stdio","command":"npx","args":["-y","@theyahia/voximplant-mcp"],"env":{"VOXIMPLANT_ACCOUNT_ID":"<VOXIMPLANT_ACCOUNT_ID value>","VOXIMPLANT_API_KEY":"<your VOXIMPLANT_API_KEY>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "voximplant": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add voximplant --env 'VOXIMPLANT_ACCOUNT_ID=<VOXIMPLANT_ACCOUNT_ID value>' --env 'VOXIMPLANT_API_KEY=<your VOXIMPLANT_API_KEY>' -- npx -y @theyahia/voximplant-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.voximplant]
command = "npx"
args = ["-y", "@theyahia/voximplant-mcp"]
env = { VOXIMPLANT_ACCOUNT_ID = "<VOXIMPLANT_ACCOUNT_ID value>", VOXIMPLANT_API_KEY = "<your VOXIMPLANT_API_KEY>" }

If the file already exists, append the block to the end.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "voximplant": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "voximplant": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "voximplant": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "voximplant": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "voximplant": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "environment": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "voximplant": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "voximplant": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/voximplant-mcp"
      ],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "<VOXIMPLANT_ACCOUNT_ID value>",
        "VOXIMPLANT_API_KEY": "<your VOXIMPLANT_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

VOXIMPLANT_ACCOUNT_IDrequired
VOXIMPLANT_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit d4ecc50.

Text for your agent

Get VOXIMPLANT_ACCOUNT_ID and VOXIMPLANT_API_KEY from the manage.voximplant.com panel and connect the server with claude mcp add voximplant -e VOXIMPLANT_ACCOUNT_ID=... -e VOXIMPLANT_API_KEY=... -- npx -y @theyahia/voximplant-mcp.

Other ways from the author

{
  "mcpServers": {
    "voximplant": {
      "command": "npx",
      "args": ["-y", "@theyahia/voximplant-mcp"],
      "env": {
        "VOXIMPLANT_ACCOUNT_ID": "your-id",
        "VOXIMPLANT_API_KEY": "your-key"
      }
    }
  }
}

Standard entry for claude_desktop_config.json.

This is third-party code. Review the repository files before installing.

What it does

The server gives an agent 21 tools for Voximplant cloud telephony: call history and initiating calls, ACD and SmartQueue queue state, links to call recordings and their transcripts, sending SMS, managing VoxEngine scenarios and routing rules, phone numbers and billing. It also ships skills packaged as ready scenarios on top of the tools, such as parsing call history. The project is part of the same author's WWmcp collection, but is published as a separate npm package and repository.

Who it is for. For call centers and sales teams running Voximplant who want to review calls and trigger outbound calling through an agent.

Good fit when

You need to know how many calls were missed yesterday, with links to recordings
You need to trigger an outbound call via a routing rule
You need to send an SMS or check agent queue state

Not a fit when

You have no Voximplant account or no access to the API section in the control panel
You cannot let the agent trigger real calls and SMS without human confirmation

Example request

How many calls did we miss yesterday, and what does the ACD queue look like right now

Limitations

Authorization via account_id and api_key is officially marked deprecated by Voximplant but still functional; the server does not use the modern service-account JWT alternative. This is an unofficial community project, not a server from Voximplant itself.

How to disable. Remove the server from your MCP client config, for example claude mcp remove voximplant in Claude Code.

MCP

Transport: stdio, http
Authentication: API key

Environment variables
Environment variables
VOXIMPLANT_ACCOUNT_ID required	Voximplant account ID from the control panel.
VOXIMPLANT_API_KEY required, secret	Account API key; the vendor marks this auth method deprecated but functional.

Security check

Can trigger real outbound calls and send SMS on behalf of the account
The API key gives access to call recordings and billing

README in short

The Russian README explains the server's purpose, gives connection instructions for Claude Desktop, Claude Code, VS Code and Cursor with VOXIMPLANT_ACCOUNT_ID and VOXIMPLANT_API_KEY, and a Streamable HTTP mode. A table of 21 tools covers calls, queues, recordings, SMS, VoxEngine scenarios, routing rules, numbers and billing.

FAQ

Is this part of the WWmcp monorepo?

Yes, it belongs to the same author's WWmcp collection, but installs as its own npm package with its own repository.

Can an agent trigger outbound calls?

Yes, the start_call tool initiates an outbound call via a routing rule, passing the number to the scenario through customData.

Salesforce DX MCP Server

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483

Yandex Kit skills for store management

kit-skills

Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh riskRussian stackNo VPN needed28

YouGile MCP by Indalo

YouGile MCP

Editors’ pick

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverHigh riskRussian stackNo VPN needed

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh riskRussian stackNo VPN needed

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Salesforce DX MCP Server

Yandex Kit skills for store management

YouGile MCP by Indalo

Bitrix24 portal MCP server