Clanker
MCP server for running external coding agents as background tasks inside Claude Code. Supports multiple backends including Codex, Grok, GLM, DeepSeek, and more.
README
Clanker
Claude Code plugin + stdio MCP server for running external coding agents as Claude-owned background tasks.
Clanker exposes these slash commands:
| Command | Backend |
|---|---|
/clanker:codex <task> |
Codex ACP |
/clanker:grok <task> |
Grok ACP |
/clanker:glm <task> |
Opencode with GLM |
/clanker:deepseek <task> |
Opencode with DeepSeek |
/clanker:kimi <task> |
Opencode with Kimi |
/clanker:free <task> |
Opencode free model |
/clanker:oc <provider/model> <task> |
Advanced Opencode model override |
Default mode is background: the Claude Agent task owns the visible bottom task row, while the MCP server owns the ACP backend process. Use --wait to run foreground.
Layout
.
├── .claude-plugin/marketplace.json
├── plugin/
│ ├── .claude-plugin/plugin.json
│ ├── .mcp.json
│ ├── agents/
│ ├── commands/
│ └── dist/clanker-mcp.mjs
├── src/
├── test/
├── scripts/
└── package.json
Install
claude plugin marketplace add /path/to/ClankerHouse
claude plugin install clanker@clanker
Then restart Claude Code or run /reload-plugins.
The active Claude config should point here:
"enabledPlugins": {
"clanker@clanker": true
},
"extraKnownMarketplaces": {
"clanker": {
"source": {
"source": "directory",
"path": "/path/to/ClankerHouse"
}
}
}
Development
npm ci
npm run bundle
npm test
npm run typecheck
npm run bundle writes plugin/dist/clanker-mcp.mjs, the self-contained server bundle Claude loads from its plugin cache.
Runtime Config
| Env | Default | Meaning |
|---|---|---|
CLANKER_STALL_THRESHOLD_MS |
300000 |
Silence before a running turn is flagged as suspected stalled. |
CLANKER_TURN_TIMEOUT_MS |
2700000 |
Hard per-turn ceiling before the subprocess is killed and the turn becomes error. |
CLANKER_HANDSHAKE_TIMEOUT_MS |
30000 |
ACP initialize + session/new timeout. |
CLANKER_SESSION_TTL_MS |
600000 |
Idle session TTL before reaping. |
CLANKER_WAIT_DEFAULT_MS / CLANKER_WAIT_MAX_MS |
30000 / 55000 |
clanker_wait long-poll default and cap. |
CLANKER_PROGRESS_EXPERIMENTAL |
unset | =1 enables MCP progress notifications. |
CLANKER_MCP_BASE_REPO |
server cwd | Base repo for managed worktrees. |
CLANKER_RUNS_ROOT / CLANKER_WORKTREES_ROOT |
~/.cache/clanker/{runs,worktrees} |
Artifact and managed worktree roots. |
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.