Log inSubmit server
Omnidim MCP Server logo

Omnidim MCP Server

Controls OmniDimension voice agents, calls, and bulk campaigns from MCP-compatible clients through a local stdio server.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Omnidim MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "omnidim-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@omnidim-ai/mcp-server"
      ],
      "env": {
        "OMNIDIM_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

omnidim-mcp-server connects MCP-compatible clients to OmniDimension for managing voice agents, starting calls, reviewing call data, and operating bulk-call campaigns. It runs locally over stdio and authenticates requests with an OmniDimension API key. Use it when an agent needs to configure voice workflows, dispatch individual calls, inspect transcripts and sentiment, or manage campaign contacts and dialing behavior. Claude Desktop, Claude Code, Cursor, and Windsurf are supported installation targets.

Use cases

  • Configure and version voice agents
  • Start individual outbound calls
  • Review call transcripts and sentiment
  • Build and operate bulk-call campaigns
  • Feed contacts into dynamic campaigns

Key features

  • Voice-agent lifecycle and version management
  • Short-lived WebSocket voice sessions
  • Outbound call dispatch and call logs
  • Bulk campaigns with contact batching
  • Campaign number-pool and concurrency controls
  • Knowledge-base and provider operations

Tools52

What Omnidim MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~16.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

19/23 checks healthy over the last 90d

What it can do

From the 52 tools this server returned when we ran it; 52 declare their own safety hints.

Can delete or modify data · 15Handles credentials · 3Makes network requests · 14Read-only tools · 37
Network at startup5 connections
Files written at startup3
Install scriptsNone
npm provenanceSigned build
Package age145 days
Maintainers2

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @omnidim-ai/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed52Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Omnidim MCP Server works

What omnidim-mcp-server does

omnidim-mcp-server exposes OmniDimension operations through the Model Context Protocol. Its tools cover voice-agent configuration, live voice-session setup, individual outbound calls, call logs, and bulk calling. Agent management includes creating, updating, listing, retrieving, and deleting agents, along with saved configuration versions that can be compared, renamed, removed, or restored.

Bulk-call support extends beyond campaign creation. An MCP client can add individual or batched contacts, inspect per-contact results, manage the campaign's phone-number pool, change concurrency, pause or resume dialing, reschedule or cancel campaigns, retry unsuccessful contacts, and apply daily calling windows. Call-log tools provide details such as duration, status, transcript, sentiment, extracted variables, and recording identifiers.

The package also exposes operations for knowledge bases, phone numbers, provider catalogs, and reseller accounts. Reseller functions are limited to reseller accounts.

How it works

The package is a local stdio MCP server. An MCP client launches it with npx, and the server sends authenticated requests to OmniDimension using OMNIDIM_API_KEY. The setup command can save and reuse an API key from the local OmniDimension credentials file, or prompt for and validate a new key.

For a live voice conversation, createSession reserves a short-lived, single-use session and returns a WebSocket URL. Creating the session does not begin audio; the client must connect to that URL. Applications should keep the API key on the server and pass only the returned URL to a client.

Paginated operations return a cursor for the next page. For bulk-call lines, continue requesting pages with the returned opaque cursor until it is null. The line records contain recording identifiers rather than full transcripts; retrieve the corresponding call log when transcript data is needed.

Setup and configuration

The quickest installation is:

Terminal
npx -y @omnidim-ai/mcp-server setup

The setup flow can install the server in detected Claude Code, Claude Desktop, Cursor, and Windsurf configurations. Manual configurations run the package with npx -y @omnidim-ai/mcp-server and provide the API key through the OMNIDIM_API_KEY environment variable. An API key is obtained from OmniDimension's API management page.

For local development, clone the repository, install dependencies, build the package, and start it with the environment variable set:

Terminal
npm install
npm run build
OMNIDIM_API_KEY=sk_... npm start

The doctor command reports versions, detected clients, backend reachability, and recent errors without printing the API key. Anonymous telemetry can be disabled with npx -y @omnidim-ai/mcp-server telemetry disable.

Tools and capabilities

  • Create and manage OmniDimension voice agents, including configuration versions.
  • Create short-lived voice sessions and receive WebSocket connection URLs.
  • Dispatch calls to phone numbers that include a country code.
  • List call logs and retrieve detailed call information.
  • Create, start, pause, resume, reschedule, cancel, and inspect bulk campaigns.
  • Add contacts individually or in batches of up to 1,000.
  • Manage campaign number pools, active dialing states, concurrency, retries, and calling windows.
  • Inspect agents, LLMs, voices, speech providers, phone numbers, and knowledge bases.

Limitations and notes

Voicemail detection requires account-level access before its configuration can be used. Restoring an agent version saves the current setup as a backup, but deleted knowledge files or integrations cannot be re-linked automatically and are reported as skipped.

A running bulk campaign cannot pause its final active number. Phone numbers added to a campaign must belong to the account and cannot already be assigned to a different agent. Bulk-call line pages return recording identifiers instead of transcripts, so large transcript payloads must be fetched from the related call log.

The package sends limited anonymous usage and error-category telemetry. It does not send API keys, tool inputs or outputs, personal information, or local file paths. A local error log is kept at ~/.config/omnidim/logs/mcp.log.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Omnidim MCP Server

omnidim-mcp-server is an MCP server that connects MCP clients to OmniDimension's voice platform. Its main tools create and manage voice agents, open short-lived voice sessions, dispatch calls, retrieve call logs, and create or operate bulk-call campaigns with contacts, numbers, scheduling, and retries.

Run `npx -y @omnidim-ai/mcp-server setup` to install it and configure detected MCP clients. The setup command reuses a saved credential when available or prompts for an OmniDimension API key. Manual installation runs the package with `OMNIDIM_API_KEY` in the client environment.

Yes, omnidim-mcp-server supports Claude Desktop, Cursor, and Windsurf, as well as Claude Code. The setup command can detect and configure these clients, or you can add a stdio entry that launches the package with `npx` and supplies `OMNIDIM_API_KEY`.

Call `createSession` to receive a single-use, expiring `ws_url`, then have the client connect to that URL over WebSocket. Creating the session does not start audio. Keep the OmniDimension API key on your server and return only the WebSocket URL to the client.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOmnidim MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/omnidim-mcp-server?style=directory)](https://allmcps.com/mcp/omnidim-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/omnidim-mcp-server"><img src="https://allmcps.com/api/badge/omnidim-mcp-server?style=directory" alt="Omnidim MCP Server on AllMCPs" /></a>