
Sprout MCP
io.github.mepsoptiPublished by GitHub account mepsoptiv0.1.4Updated Oct 24, 2026
Model-tiered content pipeline — cheap models seed, expensive models verify
Overview
A local MCP server that runs a model-tiered content pipeline: cheap models draft, mid-tier models fact-check, and expensive models verify, with provenance and a
- What you can do
- Store content chunks with provenance, task type and sources, and list chunks needing review filtered by confidence or project. Promote chunks through seed, watered and sprouted stages or reject them. Get model-tier recommendations per task type and add or update routing rules at runtime. View chunk counts, confidence levels, token usage and estimated spend per model. Export verified chunks as JSON and generate structured review summaries for batch verification. Schedule, list and cancel tasks, and track failed attempts with backoff guidance.
- When to use it
- Useful when you generate a lot of content through a multi-model pipeline and want to keep most work on cheaper models while reserving an expensive model for final verification. Also fits workflows that need per-chunk provenance, confidence tracking and cost reporting.
- Requirements
- Runs locally as a Python package launched with uvx, so a Python/uv runtime is needed. Uses a local SQLite database, by default under the user's home directory. Optional environment variables set the database path, a JSON config file for custom routes and pricing, and retry limits and backoff.
Installation
In SourceWeft
- Open Sprout MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Or add to Claude Code's MCP config (~/.claude/settings.json):
How It Works
- 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)
Configuration
Environment Variables
Custom Config File
Create a JSON file and point SPROUT_CONFIG at it:
Default Routing Table
Unknown task types default to haiku — start cheap, escalate if needed.
Example Workflow
Development
Support
If Sprout saves you money on your AI bill, consider buying me a coffee:
License
MIT
mcp-name: io.github.mepsopti/sprout-mcp
Source: README.md at commit 65186aa
Tools
0Version history
1- v0.1.4LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts