Llmtest MCP vs MCP Rubber Duck
A side-by-side look at the Llmtest MCP and MCP Rubber Duck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Llmtest MCP for conversational ai work as a local process; choose MCP Rubber Duck 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 Llmtest MCP when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LLMTEST_API_KEY, LLMTEST_BASE_URL. - You want tools like
status, list_flows, get_suggestions.
Choose MCP Rubber Duck 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.
- You want tools like
ask_duck, chat_with_duck, clear_conversations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 51/100 · Good | 68/100 · Great |
| 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 | LLMTEST_API_KEYLLMTEST_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 180 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 15 | 15 |
| Full listing | View Llmtest MCP | View MCP Rubber Duck |
Tools & capabilities
Llmtest MCP tools 15
statusShow proxy status and activity summarylist_flowsList all AI flows with cost and latency statsget_suggestionsGet pending model-switch recommendationsupdate_suggestionAccept or dismiss a suggestionrun_benchmarkBenchmark a flow against challenger modelsoptimize_promptRewrite a flow's prompt and find a cheaper model that still worksseed_samplesAdd test prompts for pre-launch benchmarkinglist_samplesShow stored test samples per flowlist_new_modelsShow new and trending modelsget_accountCheck credit balance and usageget_autopilot_statusCheck whether autopilot is on and whether the account is eligibleenable_autopilotTurn on weekly auto-optimization with safety gates + drift-based auto-revert- +3 more on the listing page
MCP Rubber Duck tools 15
ask_duckAsk a single question to a specific LLM providerchat_with_duckConversation with context maintained across messagesclear_conversationsClear all conversation historylist_ducksList configured providers and health statuslist_modelsList available models for providerscompare_ducksAsk the same question to multiple providers simultaneouslyduck_councilGet responses from all configured ducksget_usage_statsUsage statistics and estimated costsduck_voteMulti-duck voting with reasoning and confidenceduck_judgeHave one duck evaluate and rank others' responsesduck_iterateIteratively refine a response between two ducksduck_debateStructured multi-round debate between ducks- +3 more on 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.
Llmtest MCP
{
"mcpServers": {
"llmtest-mcp": {
"command": "npx",
"args": [
"-y",
"llmtest-mcp"
],
"env": {
"LLMTEST_API_KEY": "YOUR_LLMTEST_API_KEY_HERE",
"LLMTEST_BASE_URL": "YOUR_LLMTEST_BASE_URL_HERE"
}
}
}
}
MCP Rubber Duck
{
"mcpServers": {
"nesquikm-mcp-rubber-duck": {
"command": "npx",
"args": [
"-y",
"mcp-rubber-duck"
]
}
}
}
Frequently asked questions
Llmtest MCP is categorized under Conversational AI and uses a local stdio subprocess. MCP Rubber Duck belongs to Conversational AI and uses a local stdio subprocess. Pick Llmtest MCP for conversational ai work and MCP Rubber Duck 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.
Llmtest MCP has no declared pricing — check the project's own site. MCP Rubber Duck 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 llmtest-mcp and nesquikm-mcp-rubber-duck as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Llmtest MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. MCP Rubber Duck has 68/100 (Great) with 5 views, 0 installs and 180 GitHub stars.