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
Metadata
Release files for sprout-mcp 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sprout_mcp-0.1.4.tar.gz | 70.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sprout_mcp-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 86.6 kB
Release files / sprout_mcp-0.1.4.tar.gz
| Download URL | sprout_mcp-0.1.4.tar.gz |
|---|---|
| Size | 70.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a91499298902a73b49ea8d9e9b8e917f67c1935e353d0c69bb8ef6ba6c2ba960
|
|
BLAKE2b-256 checksum How to use checksums |
748ec247f01d45ee827ab2fb158df85071ea39d728b7db6cd238c898eed064ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.6 {"installer":{"name":"uv","version":"0.10.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / sprout_mcp-0.1.4-py3-none-any.whl
| Download URL | sprout_mcp-0.1.4-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed1dd4aaf57017597016547d2c413e42fd9fb45bcf091c2b87a11dc21e151d7d
|
|
BLAKE2b-256 checksum How to use checksums |
efa9b1e3ca4765706092468c52a72401d73f9d262c795302ad8e560120705036
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.6 {"installer":{"name":"uv","version":"0.10.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for sprout-mcp 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.