Keshro MCP
The intelligent execution layer for coding agents, exposed as an MCP server for high-stakes engineering projects.
pip install keshro-mcp
When to use this vs the CLI
Use the CLI (pip install keshro) for the full experience: interactive clarifying questions, migration detection, parallel execution in isolated worktrees, git checkpoints, cross-task context routing, and cost tracking.
Use MCP if your agent platform speaks MCP and you want direct tool-call access to Keshro plans and tasks.
The CLI gives you more control. MCP is more flexible for custom integrations.
Setup
Set your API token:
export KESHRO_API_TOKEN="ksh_pat_..."
Get one from keshro.com/account.
Connect to your agent
MCP works with any agent that supports the protocol — Claude Code, Cline, Continue, Zed, and others.
Claude Code — add to ~/.claude.json:
{
"mcpServers": {
"keshro": {
"command": "keshro-mcp",
"env": { "KESHRO_API_TOKEN": "ksh_pat_..." }
}
}
}
Other MCP clients — point your client at the keshro-mcp binary with KESHRO_API_TOKEN set in the environment. The server uses stdio transport.
Available tools
| Tool | What it does |
|---|---|
preview_plan |
Run Keshro's pre-plan intake and clarifying-question preview |
generate_plan |
Generate a plan from a description using AI |
list_plans |
List all plans |
get_plan |
Get a plan with all tasks |
plan_status |
Progress summary (task counts, enrichment sources) |
next_task |
Get the next actionable task |
create_plan |
Create a plan manually |
start_task |
Mark a task as in progress |
complete_task |
Mark a task as done |
block_task |
Mark a task as blocked |
unblock_task |
Clear a blocker |
append_task_note |
Add a note to a task |
add_task_artifact |
Attach an artifact link |
record_decision |
Log a decision with context, choice, and reasoning |
edit_task |
Edit task title or description |
push_to_tracker |
Push tasks to Linear, Jira, or GitHub as issues |
sync_pull |
Pull status updates from connected issue tracker |
export_project |
Export project data |
Current parity notes
MCP now supports the newer task controls exposed in the web product:
- explicit
depends_ontask dependencies parallelizabletask scheduling hints- per-task
executorselection - generic issue linking via
issue_id, plus external issue fields - pre-plan intake via
preview_plan
It still remains thinner than the CLI for actual execution orchestration. The CLI owns parallel local worktrees, git checkpoints, richer execution transcripts, and the direct keshro continue runtime loop.
License
MIT
Releases
Publish the MCP package with one GitHub Actions run after you bump pyproject.toml:
gh workflow run "Publish MCP"
That workflow reads the package version from pyproject.toml, publishes the package to PyPI, then creates the matching vX.Y.Z GitHub release automatically.
1 maintainer
Metadata
1 maintainer
Release files for keshro-mcp 0.1.42
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| keshro_mcp-0.1.42.tar.gz | 10.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| keshro_mcp-0.1.42-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.1 kB
Release files / keshro_mcp-0.1.42.tar.gz
| Download URL | keshro_mcp-0.1.42.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b5f3eae530ee4773c8c916aae585f67194311d2ad79c53200c7eca970d93fbb
|
|
BLAKE2b-256 checksum How to use checksums |
99433ae40c979ec735267b4db8c275f69782ebdc774adb212a9da217062640b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 30, 2026.
Transparency logRelease files / keshro_mcp-0.1.42-py3-none-any.whl
| Download URL | keshro_mcp-0.1.42-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e110297febdecd32739d8d549cc21f879f854a3cd83e2e3ad1122a7ec1584bac
|
|
BLAKE2b-256 checksum How to use checksums |
4ef813761af4f68c36932bc7861014a36b483d5ef01fa74c8008055472c51635
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 30, 2026.
Transparency log
