Tokentrust vs Voice MCP
A side-by-side look at the Tokentrust and Voice MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tokentrust for conversational ai work as a local process; choose Voice MCP 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?
Choose Tokentrust when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 44/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1,415 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Tokentrust | View Voice MCP |
Tools & capabilities
Tokentrust tools
No tool names declared yet. Check the project README from the listing page.
Voice MCP 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.
Tokentrust
{
"mcpServers": {
"tokentrust": {
"command": "npx",
"args": [
"-y",
"tokentrust-cli"
]
}
}
}
Voice MCP
{
"mcpServers": {
"mbailey-voice-mcp": {
"command": "uvx",
"args": [
"voice-mode-install"
]
}
}
}
Frequently asked questions
Tokentrust is categorized under Conversational AI and uses a local stdio subprocess. Voice MCP belongs to Conversational AI and uses a local stdio subprocess. Pick Tokentrust for conversational ai work and Voice MCP 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.
Tokentrust has no declared pricing — check the project's own site. Voice MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 tokentrust and mbailey-voice-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tokentrust has a quality signal of 44/100 (Fair) with 4 views, 0 installs and 0 GitHub stars. Voice MCP has 59/100 (Good) with 3 views, 0 installs and 1,415 GitHub stars.