Voice MCP vs .prompts
A side-by-side look at the Voice MCP and .prompts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
.
.promptsConversational AI · Remote HTTP/SSE.prompts, the home to all your AI prompts, everywhere you need them.39FairAuth: oauth 2.0Verdict: choose Voice MCP for conversational ai work as a local process; choose .prompts for conversational ai over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
.Choose .prompts when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | . .prompts | |
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 60/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | OAuth 2.0 |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,417 | — |
| Directory activity | 5 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Voice MCP | View .prompts |
Tools & capabilities
Voice MCP tools
No tool names declared yet. Check the project README from the listing page.
.prompts tools
No tool names declared yet. Check the project README from the listing page.
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": {
"mbailey-voice-mcp": {
"command": "uvx",
"args": [
"voice-mode-install"
]
}
}
}
.prompts
{
"mcpServers": {
"prompts": {
"command": "npx",
"args": [
"-y",
"prompts"
]
}
}
}
Frequently asked questions
Voice MCP is categorized under Conversational AI and uses a local stdio subprocess. .prompts belongs to Conversational AI and uses a remote HTTP/SSE transport. Pick Voice MCP for conversational ai work and .prompts 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. .prompts has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 prompts 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 60/100 (Good) with 5 views, 0 installs and 1,417 GitHub stars. .prompts has 39/100 (Fair) with 6 views, 0 installs and 0 GitHub stars.