Voice MCP vs Mdma

A side-by-side look at the Voice MCP and Mdma MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Voice MCP logoVoice MCPConversational AI · Local subprocess (stdio)Complete voice interaction server supporting speech-to-text, text-to-speech, and real-time voice conversations through local microphone, OpenAI-compatible APIs, and LiveKit integration59GoodAuth: api key requiredMdma logoMdmaConversational AI · Local subprocess (stdio)MCP server for MDMA — exposes spec, prompts, docs, and package metadata to AI assistants.59GoodAuth: not declared

Verdict: choose Voice MCP for conversational ai work as a local process; choose Mdma for conversational ai as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Voice MCP logoChoose Voice MCP when

  • You need dedicated capabilities in the Conversational AI domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Voice MCP

Mdma logoChoose Mdma when

  • You need dedicated capabilities in the Conversational AI domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get-spec, get-prompt, list-prompt-variants.
Explore Mdma

Feature & specification comparison

Rows where the two servers differ are marked.

SpecVoice MCP logoVoice MCPMdma logoMdma
CategoryConversational AIConversational AI
Quality signal59/100 · Good59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingBYOK (pay the provider)Not declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,41671
Directory activity 3 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed8

Tools & capabilities

Voice MCP tools

No tool names declared yet. Check the project README from the listing page.

Mdma tools 8

  • get-specReturns the full MDMA specification: component types, JSON schemas, binding syntax, external data sources (`{ source, params }` refs and the `rows` / `series` / `options` kinds), and authoring rules
  • get-promptReturns a named prompt (`mdma-author`, `mdma-reviewer`, or `mdma-fixer`). For `mdma-author`, accepts an optional `variantId` (e.g. `google/gemini-2.5-pro`) to return the model-optimised variant
  • list-prompt-variantsReturns all available `MDMA_AUTHOR` prompt variants (id, label, description) — use the id with `get-prompt` to fetch the model-optimised prompt
  • build-system-promptGenerates a custom MDMA prompt from structured input (domain, components, fields, steps, business rules). Pass `dataSources` (an external data-source catalog of `rows` / `series` / `options` entries) to get the full system prompt with the catalog and the rule to reference data via `{ source, params…
  • validate-promptValidates a custom prompt against MDMA conventions — returns warnings, suggestions, and constraint reference
  • list-packagesReturns all MDMA packages with purpose, install command, and usage example
  • list-docsReturns the catalog of MDMA documentation files (path, title, description) available for fetching from the public GitHub repo
  • get-docFetches the latest version of an MDMA documentation file from `raw.githubusercontent.com/MobileReality/mdma`. Supports optional `ref` (branch/tag/SHA, defaults to `main`)

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Voice MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mbailey-voice-mcp": {
      "command": "uvx",
      "args": [
        "voice-mode-install"
      ]
    }
  }
}

Mdma

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mdma": {
      "command": "npx",
      "args": [
        "-y",
        "@mobile-reality/mdma-cli"
      ]
    }
  }
}

Frequently asked questions

Voice MCP is categorized under Conversational AI and uses a local stdio subprocess. Mdma belongs to Conversational AI and uses a local stdio subprocess. Pick Voice MCP for conversational ai work and Mdma for conversational ai.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Voice MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Mdma has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mbailey-voice-mcp and mdma as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Voice MCP has a quality signal of 59/100 (Good) with 3 views, 0 installs and 1,416 GitHub stars. Mdma has 59/100 (Good) with 2 views, 0 installs and 71 GitHub stars.