A curated registry of agent stacks: search by job, get the tools, prompt, and install plan.
Connect Remote server
claude mcp add --transport http runchr https://api.runchr.com/mcp
{
"mcpServers": {
"runchr": {
"url": "https://api.runchr.com/mcp"
}
}
}
{
"servers": {
"runchr": {
"type": "http",
"url": "https://api.runchr.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.runchr.com/mcp
Tools 4 found in our last check
search_stacksFind 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.
get_stackOne stack's card: its copy, its tools, its tier, and its revision.
get_manifestThe manifest a loader runs: the tools, the model, the harness, and the prompt. This is the thing to install.
get_install_planHow 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.
Details
| Endpoint | https://api.runchr.com/mcp (Streamable HTTP) |
| First published | 6 Nov 2026 |
| Last updated | 6 Nov 2026 |
| Registry name | io.github.rmngl/runchr |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
