runchr
A curated registry of agent stacks: search by job, get the tools, prompt, and install plan.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"runchr": {
"url": "https://api.runchr.com/mcp"
}
}
}Remote endpoints
https://api.runchr.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (4)
🟢search_stacks(query, topic, limit)
Find agent stacks by problem domain or text. A query is split into words and any of them may match, against the name, the copy, and the prompt. When nothing matches, the reply is labelled and filled with the most established stacks.
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "What the agent needs to do, in your own words. Split into words; any may match."
},
"topic": {
"type": "string",
"description": "A problem domain id, e.g. software-devops."
},
"limit": {
"type": "integer",
"description": "How many stacks to return (default 10)."
}
}
}🟢get_stack(owner, slug)
One stack's card: its copy, its tools, its tier, and its revision.
Input Schema
{
"type": "object",
"properties": {
"owner": {
"type": "string",
"description": "The stack's namespace owner (a login, or runchr)."
},
"slug": {
"type": "string",
"description": "The stack's slug."
}
},
"required": [
"owner",
"slug"
]
}🟢get_manifest(owner, slug)
The manifest a loader runs: the tools, the model, the harness, and the prompt. This is the thing to install.
Input Schema
{
"type": "object",
"properties": {
"owner": {
"type": "string",
"description": "The stack's namespace owner (a login, or runchr)."
},
"slug": {
"type": "string",
"description": "The stack's slug."
}
},
"required": [
"owner",
"slug"
]
}🟢get_install_plan(owner, slug)
How to install a stack: the MCP servers to configure, the shell commands to run, and the notes (a path, a harness command) for the rest. Deciding and configuring are open; the agent's host runs the commands.
Input Schema
{
"type": "object",
"properties": {
"owner": {
"type": "string",
"description": "The stack's namespace owner (a login, or runchr)."
},
"slug": {
"type": "string",
"description": "The stack's slug."
}
},
"required": [
"owner",
"slug"
]
}Community
Evidence