llmtest-mcp
MCP server that benchmarks AI models on your actual prompts and finds cheaper, faster alternatives.
README
LLMTest MCP Server
<!-- mcp-name: io.github.tjacquesson/llmtest-mcp -->
MCP server that benchmarks AI models on your actual prompts and finds cheaper, faster alternatives. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible tool.
Quick Start
1. Get your API key
Sign up at llmtest.io and grab your API key from the dashboard.
2. Add to your tool
Claude Code:
claude mcp add llmtest -- npx llmtest-mcp
Then set your key:
export LLMTEST_API_KEY=llmt_your_key_here
Cursor / Windsurf / Other MCP clients:
Add to your MCP config file:
{
"mcpServers": {
"llmtest": {
"command": "npx",
"args": ["llmtest-mcp"],
"env": {
"LLMTEST_API_KEY": "llmt_your_key_here"
}
}
}
}
3. Talk to your AI
Just ask in natural language:
- "Check my LLMTest status"
- "Find cheaper models for my AI calls"
- "Run a benchmark on my blog-writer flow"
- "What models are trending?"
How It Works
LLMTest is a proxy that sits between your app and AI providers. Point your app at https://llmtest.io/v1 instead of calling OpenAI/Anthropic directly, and LLMTest tracks your usage, benchmarks alternatives, and suggests cost savings.
This MCP server gives your AI assistant access to LLMTest's tools so it can manage everything for you.
Available Tools
| Tool | Description |
|---|---|
status |
Show proxy status and activity summary |
list_flows |
List all AI flows with cost and latency stats |
get_suggestions |
Get pending model-switch recommendations |
update_suggestion |
Accept or dismiss a suggestion |
run_benchmark |
Benchmark a flow against challenger models |
optimize_prompt |
Rewrite a flow's prompt and find a cheaper model that still works |
seed_samples |
Add test prompts for pre-launch benchmarking |
list_samples |
Show stored test samples per flow |
list_new_models |
Show new and trending models |
get_account |
Check credit balance and usage |
get_autopilot_status |
Check whether autopilot is on and whether the account is eligible |
enable_autopilot |
Turn on weekly auto-optimization with safety gates + drift-based auto-revert |
disable_autopilot |
Turn off autopilot (existing optimizations stay active) |
list_active_optimizations |
List auto-accepted optimizations still inside their 24h revert window |
revert_optimization |
Roll an auto-accepted optimization back to the previous prompt |
Autopilot
Autopilot automatically optimizes your flows on a weekly cadence. Changes that pass every safety gate go live with a 24-hour revert window. Drift detection keeps checking after that and rolls back if quality slips.
To enable from your IDE: ask your AI assistant something like "enable LLMTest autopilot". It will call enable_autopilot. Use get_autopilot_status to confirm prerequisites.
Prerequisites (checked per flow each cycle):
- Autopilot enabled on the account
- Email verified
- Account age ≥ 14 days (trust ramp)
- Flow has ≥ 20 real calls in the last 7 days
- Flow not optimized by autopilot in the last 14 days (cooldown)
- Positive credit balance (~$1–2 per run)
Safety gates (all must pass for auto-accept): 95% CI lower bound > 50% win rate, multi-judge agreement ≥ 80%, ≥ 20% total savings, no length-bias warning, golden-set regression check.
Revert: 24h window after auto-accept. After that, only drift detection can roll back.
Typical Workflow
Pre-launch (no traffic yet):
- Tell your AI: "I'm building a support chatbot using gpt-4o"
- It seeds realistic test samples with
seed_samples - It runs
run_benchmarkto compare models - It shows you
get_suggestionswith cheaper alternatives
Post-launch (with real traffic):
- Route your AI calls through
https://llmtest.io/v1 - LLMTest monitors usage and auto-benchmarks when flows hit 50+ calls
- Ask "any cost-saving suggestions?" to see recommendations
- Accept a suggestion and update your code
Environment Variables
| Variable | Required | Description |
|---|---|---|
LLMTEST_API_KEY |
Yes | Your API key from llmtest.io/dashboard |
LLMTEST_BASE_URL |
No | Custom API URL (defaults to https://llmtest.io) |
Links
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。