sprout-mcp
A model-tiered content pipeline that routes tasks to the appropriate AI model tier (Haiku, Sonnet, Opus) to optimize cost and quality, with provenance tracking and automatic review workflow.
README
Sprout MCP
Drop your Opus bill 80%. Model-tiered content pipeline for MCP — cheap models seed work, expensive models verify it.
Sprout routes tasks to the right model tier automatically. Haiku drafts, Sonnet fact-checks, Opus verifies. Every chunk tracks provenance, confidence, and cost.
Install
uvx sprout-mcp
Or add to Claude Code's MCP config (~/.claude/settings.json):
{
"mcpServers": {
"sprout": {
"command": "uvx",
"args": ["sprout-mcp"]
}
}
}
How It Works
Haiku (seed) → Sonnet (watered) → Opus (sprouted)
Draft Fact-check Verify
$0.005/M $0.015/M $0.075/M
- Seed — Haiku drafts content cheaply (summarization, extraction, first passes)
- Water — Sonnet reviews and fact-checks the seeds
- Sprout — Opus deep-verifies only what passed Sonnet's review
Instead of running everything through Opus at $75/M output tokens, most work stays at Haiku's $5/M. Only the final verification — typically 10-20% of total work — touches Opus.
Tools (13)
| Tool | Description |
|---|---|
submit_chunk |
Store content with provenance (model, task type, sources) |
get_review_queue |
List chunks needing review, filtered by confidence/project |
mark_reviewed |
Promote (seed→watered→sprouted) or reject chunks |
recommend_model |
Get model recommendation for a task type |
get_stats |
Dashboard of chunk counts, confidence levels, token usage |
export_chunks |
Export verified chunks as JSON |
opus_test |
Generate structured review summary for batch verification |
schedule_task |
Schedule tasks to run at a specific time or delay |
list_scheduled |
View pending scheduled tasks |
cancel_scheduled |
Cancel a pending scheduled task |
configure_routing |
Add/update routing rules at runtime |
get_cost_report |
Estimated spend per model with real pricing |
retry_on_error |
Track failed attempts with backoff guidance |
Configuration
Environment Variables
| Variable | Default | Description |
|---|---|---|
SPROUT_DB_PATH |
~/.sprout/sprout.db |
SQLite database location |
SPROUT_CONFIG |
(none) | Path to JSON config file for custom routes and pricing |
SPROUT_MAX_RETRIES |
3 |
Max retry attempts before giving up |
SPROUT_RETRY_BACKOFF |
2.0 |
Exponential backoff base (seconds) |
Custom Config File
Create a JSON file and point SPROUT_CONFIG at it:
{
"routes": {
"code_review": { "tier": "sonnet", "reason": "Code analysis needs reasoning" },
"translation": { "tier": "haiku", "reason": "Straightforward language task" }
},
"pricing": {
"custom-model": 10.00
}
}
Default Routing Table
| Task Type | Tier | Why |
|---|---|---|
biography_synthesis |
haiku | Factual summarization |
council_description |
haiku | Historical summarization |
document_synopsis |
haiku | Content summarization |
json_validation |
haiku | Structural verification |
summarization |
haiku | General summarization |
data_extraction |
haiku | Structured extraction |
fact_check_first_pass |
sonnet | Cross-reference claims |
code_review |
sonnet | Code analysis |
fact_check_final |
opus | Deep factual verification |
theological_analysis |
opus | Domain expertise required |
complex_analysis |
opus | Deep reasoning required |
Unknown task types default to haiku — start cheap, escalate if needed.
Example Workflow
You: Use recommend_model for "biography_synthesis"
Sprout: biography_synthesis → haiku-4.5 (Factual summarization)
You: Use submit_chunk to store the Haiku output
Sprout: Stored chunk abc12345 [seed] for person-001.biography
You: Use get_review_queue to see what needs fact-checking
Sprout: 1 chunk pending review
You: Use mark_reviewed to promote after Sonnet fact-checks it
Sprout: Chunk abc12345 → watered (verified by sonnet-4.6)
You: Use get_cost_report
Sprout: haiku-4.5: ~1,300 tokens (1 chunk) — $0.0065
Total: $0.0065
Development
git clone https://github.com/mepsopti/sprout-mcp.git
cd sprout-mcp
uv sync --extra dev
uv run pytest
Support
If Sprout saves you money on your AI bill, consider buying me a coffee:
License
MIT
mcp-name: io.github.mepsopti/sprout-mcp
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。