What is the key difference between Vox and Receptionist Toolkit?

Vox belongs to the Text-to-Speech category with local stdio execution, while Receptionist Toolkit belongs to the Text-to-Speech category with cloud HTTP/SSE execution.

How do I install Vox or Receptionist Toolkit in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Vox and Receptionist Toolkit free or paid?

Vox operates under a Free / Open Source model (No auth required). Receptionist Toolkit operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Vox lists 0 tools with 0 views and 0 GitHub stars. Receptionist Toolkit lists 0 tools with 1 views and 0 GitHub stars.

Can I use both Vox and Receptionist Toolkit together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Vox vs Receptionist Toolkit

In-depth architectural comparison of the Vox and Receptionist Toolkit MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Vox

Text-to-Speech · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Receptionist Toolkit

Text-to-Speech · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Vox if you need specialized Text-to-Speech tools running via a local process. Choose Receptionist Toolkit if your workspace requires Text-to-Speech integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Vox when:

You need dedicated capabilities in the Text-to-Speech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Vox Details

Choose Receptionist Toolkit when:

You need dedicated capabilities in the Text-to-Speech domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Receptionist Toolkit Details

Feature & Specification Comparison

Specification	V Vox Text-to-Speech	R Receptionist Toolkit Text-to-Speech
Summary	Native macOS MCP server for voice I/O — Swift binary, SFSpeechRecognizer + ElevenLabs TTS.	Free receptionist tools: phone scripts, IVR menus (EN+ES), ElevenLabs prompts, missed-call math
Category & Scope	Text-to-Speech	Text-to-Speech
Quality signal

Tools & Capabilities Breakdown

Vox Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Receptionist Toolkit Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Vox Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vox": {
      "command": "npx",
      "args": [
        "-y",
        "vox"
      ]
    }
  }
}

Receptionist Toolkit Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "receptionist-toolkit": {
      "url": "https://lobbyvoices.com/developers"
    }
  }
}

Frequently Asked Questions

Vox is categorized under Text-to-Speech and uses a local stdio subprocess. In contrast, Receptionist Toolkit belongs to Text-to-Speech using remote streaming HTTP/SSE transport. Select Vox when you need capabilities focused on text-to-speech and Receptionist Toolkit when you require tools for text-to-speech.

More alternatives to Vox More alternatives to Receptionist Toolkit Text-to-Speech category hub Canonical compare URL