runchr

io.github.rmnglPublished by GitHub account rmnglv0.1.0Updated Nov 6, 2026

A curated registry of agent stacks: search by job, get the tools, prompt, and install plan.

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

A remote registry of curated agent stacks that lets an assistant search stacks, read their manifests, and get install plans.

What you can do
  • Search agent stacks by problem domain or free text, newest first, where each stack is a runnable combination of registry tools.
  • Read one stack's card: its copy, its tools, its tier, and its revision.
  • Fetch the manifest a loader runs, covering the tools, model, harness, and prompt.
  • Get an install plan for a stack: the MCP servers to configure, the shell commands to run, and notes such as a path or harness command.
When to use it
Useful when you want to find a ready-made combination of MCP tools and prompts for a particular job, inspect what it contains, and get step-by-step setup instructions instead of assembling a stack yourself.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, or headers are declared. The client connects to the hosted API, so network access is needed.
Before you install
Install plans include shell commands that the agent's host is expected to run; review them before executing. The server only returns plans and does not run them itself. No authentication is declared, so treat returned content as third-party material.

Installation

In SourceWeft

  1. Open runchr in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rmngl%2Frunchr/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "runchr": {
      "type": "http",
      "url": "https://api.runchr.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

search_stacks

Find agent stacks by problem domain or text. Returns the newest first. Each stack is a runnable combination of registry tools.

Parameterslimitquerytopic

get_stack

One stack's card: its copy, its tools, its tier, and its revision.

Parametersslugrequiredownerrequired

get_manifest

The manifest a loader runs: the tools, the model, the harness, and the prompt. This is the thing to install.

Parametersslugrequiredownerrequired

get_install_plan

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.

Parametersslugrequiredownerrequired

Version history

1
  1. v0.1.0LatestNov 6, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.