RAPPMCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RAPPMCP run the stock_price agent for AAPL"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RAPPMCP
One MCP server for a whole folder of RAPP agent.py files.
MCP made every capability a server. agent.py makes every capability a file. One runner gives you both. Drop a file in the folder and it is a tool. No server per tool, no config per tool.
RAPPMCP is the full RAPP ecosystem as MCP: a Brainstem distro built on
brainstem-mcp, the one engine. The
grail kernel stays unchanged; brainstem-mcp wraps it in MCP; RAPPMCP adds only
its agents. distro.json is the whole distro: the kernel pin plus every file in
agents/, each pinned by sha256. rappmcp serve <folder> works as it always
has, as a thin alias over brainstem-mcp's engine.
Set up
Python 3.10 or newer, on Linux, macOS or Windows. Install it from git with pip or uv:
pip install "git+https://github.com/kody-w/rappmcp"
uv tool install "git+https://github.com/kody-w/rappmcp"Either gives you a rappmcp command. To run it without installing:
uvx --from "git+https://github.com/kody-w/rappmcp" rappmcp serve <folder>.
For work on RAPPMCP itself:
git clone https://github.com/kody-w/rappmcp && cd rappmcp
python3 -m venv .venv && .venv/bin/pip install -e .No Brainstem is needed. If ~/.brainstem has the pinned kernel file, RAPPMCP
uses it. If not, it fetches basic_agent.py once over HTTPS from the grail at
the commit in kernel.json, checks its sha256, and keeps it in
~/.cache/rappmcp (or $XDG_CACHE_HOME/rappmcp, or $RAPPMCP_CACHE). With
--kernel /path/to/basic_agent.py it uses that file.
Related MCP server: agent-3md
Use it
Point it at one agent file, or at a folder you choose. It serves nothing you did not name.
Use it from Grok Bot
Grok Bot runs stdio MCP servers on its own computer, a Linux machine, not on your Mac. So RAPPMCP and the agent folder both live there.
Ask the bot to run this on its computer:
pip install "git+https://github.com/kody-w/rappmcp" && mkdir -p /home/box/rapp-agentsThen have it put your
*_agent.pyfiles in/home/box/rapp-agents.Add this server in Grok Bot:
{"mcpServers":{"rappmcp":{"type":"stdio","command":"rappmcp","args":["serve","/home/box/rapp-agents"],"startupTimeoutSec":60}}}
Status: not yet tested in Grok Bot itself. The suite checks what Grok Bot
needs: tool names match ^[a-zA-Z0-9_-]{1,64}$, every input schema is an
object, read-only agents carry read hints, and results are text.
Grok Bot ignores tools/list_changed. After you add, change or remove an
agent file, restart the server in Grok Bot (or ask the bot to restart its MCP
servers) to see the new tool list.
Claude Code
claude mcp add rappmcp -- rappmcp serve /path/to/my-agentsTested on macOS: claude mcp list shows it Connected.
Codex
codex mcp add rappmcp -- rappmcp serve /path/to/my-agentsNot yet tested in a Codex session. codex mcp add accepts this line.
Antigravity CLI (agy)
Not yet tested. Add the "Any MCP app" block below to agy's MCP settings. (Gemini CLI was retired for personal accounts on 2026-06-18; agy replaces it.)
Any MCP app
{
"mcpServers": {
"rappmcp": {
"command": "rappmcp",
"args": ["serve", "/path/to/my-agents"]
}
}
}If rappmcp is not on the app's PATH, give the full path to the command
(for a clone: /path/to/rappmcp/.venv/bin/rappmcp).
Options
--timeout 120: seconds one call may run before it is stopped.--scan-timeout 10: seconds one agent file may take to load before it is skipped, with a log line. Startup answers at once either way, andtools/listis ready within this time, well under the 30 to 60 seconds most MCP apps wait for a server to start.--kernel PATH: use thisbasic_agent.py.--chat-url http://localhost:7071: also offerbrainstem_chat, which asks the Brainstem at that address through its own/chat.
Try it with the two examples: rappmcp serve examples.
When the tool list changes
RAPPMCP sends notifications/tools/list_changed when a file is added, changed
or removed. Apps that do not act on it (Grok Bot is one) show the new list
after a restart of the server.
Wingman Wizard
agents/wingman_wizard_agent.py drives the Wingman Mac app through its own
wingman-cli: rappmcp serve agents. It never signs in, authorizes, types
passwords or codes, or pays, and while a bot waits on you it leaves the step
to you. The guardrails are in docs/WINGMAN.md.
RAPPMCP as a distro
brainstem-mcp serves the distro straight from distro.json, next to the
Brainstem's own chat, job_status and capabilities:
git clone https://github.com/kody-w/rappmcp
claude mcp add rappmcp -- uvx --from git+https://github.com/kody-w/brainstem-mcp brainstem-mcp --distro /path/to/rappmcp/distro.jsonA file whose bytes do not match its pin is refused. After you change an agent,
run python -m brainstem_mcp.distro pin distro.json; a test fails until you do.
How it works
Each agent becomes a tool: its name, description and parameters come from its
metadata, and a call runs perform(). Each file is scanned, and each call
runs, in its own short-lived process with a timeout, so a broken agent cannot
stop the server or hide the other tools. That engine lives in brainstem-mcp;
RAPPMCP depends on it, pinned to one commit. Keep state on disk. The full mapping is in docs/BINDING.md.
RAPPMCP uses the RAPP Brainstem kernel unchanged and only reads it: it never
writes a file (not even __pycache__) into a Brainstem install. kernel.json
pins it by commit and checksum, and a test proves the copy in use is
byte-identical.
Test
.venv/bin/pip install -r requirements-dev.txt
.venv/bin/python -m pytest -qAvailable Tools
3 toolscapabilitiesA
What this AI Brainstem can do right now: status, version, model and loaded agents.
Inputs: no named parameters. Returns: result
chatA
Send one message to the AI Brainstem and return its answer as JSON: response, session_id, model, agent_logs (the agents it used). A failure is returned as a tool error with a plain explanation. Pass the returned session_id to continue the conversation. wait=false: for work that may take minutes. Returns {status: running, session_id} at once; poll job_status(session_id) for the answer. One message at a time per session.
Inputs: user_input (required), wait, session_id. Returns: result
job_statusA
Status of a chat started with wait=false: running (with seconds so far), done (with the
answer in result) or error (with a plain explanation).
Inputs: session_id (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: chat sends a message, job_status polls an asynchronous chat job, and capabilities reports server/model/agent information. There is no overlapping purpose, and the descriptions explain exactly when to use each.
Names are all lowercase but follow different conventions: 'chat' is a bare noun, 'job_status' is a snake_case noun phrase, and 'capabilities' is a plural noun. The set is readable, but there is no consistent verb_noun or resource_action pattern.
Three tools are reasonable for a focused AI chat server: send a message, poll long-running work, and inspect capabilities. It is slightly thin but each tool earns its place.
The surface covers the core lifecycle: starting a chat, handling long-running chats asynchronously, polling their status, and discovering capabilities. Minor gaps exist around explicit session management or cancellation, but normal workflows are covered.
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
Discover and call AI agents via MCP. Supports A2A agents and platform agents with async tasks.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceTurns Claude-style skills (SKILL.md files with resources) into callable MCP tools for any agent. Discovers skills from a directory, exposes their instructions and resources, and can execute bundled helper scripts.118 PyPI410MIT
- AlicenseNot gradedqualityCmaintenanceExposes an agent's skills as MCP tools, allowing any MCP client to route requests and load skills on demand from a single .3md file.20 npm1MIT
- AlicenseNot gradedqualityCmaintenanceTurns any folder of Markdown agent skills into a local MCP server, exposing them as tools, prompts, and resources for MCP-compatible clients.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and other MCP clients to register, discover, invoke, and route Python-based tools through a lightweight JSON-RPC gateway, while tracking latency, success rates, and errors.MIT