Caboose MCP Server

fafb

Personal AI toolserver — 129 MCP tools exposed to Claude, VS Code, and chat bots via a Go server hosted on AWS ECS, with Discord OAuth, admin approval workflows, and automatic tool synchronization.

Something selfishly for me but hopefully useful for others.

⚡ NEW: Ecosystem Manager (Phases 1-6) — Discord OAuth, auto-deployment, tool creation UI, admin approval workflows, and 129 tools extracted and synchronized.

Live endpoint: https://mcp.chrismarasco.io/mcp · Web UI: https://mcp.chrismarasco.io/ui/

[!WARNING] Experimental software — use at your own risk. This project is under active development and has not been fully tested. Tools may behave unexpectedly, modify data, or fail without warning. See the Disclaimer for full terms.

Architecture

graph TD
    Claude["Claude Code (stdio)"] -->|all 118 tools| Binary["fafb (Pi)"]
    VSCode["VS Code / Bruno"] -->|HTTPS| ALB["ALB · mcp.chrismarasco.io"]
    ALB --> Serve["ECS · --serve-hosted\n68 hosted tools"]
    Slack["Slack"] --> Bots["ECS · --bots\nSlack + Discord gateway"]
    Discord["Discord"] --> Bots
    Bots -->|Claude Haiku| Agent["Bot agent loop"]
    Binary -->|LAN MQTT| Bambu["Bambu A1 Printer"]
    Binary -->|socket| DockerD["Docker daemon"]
    Serve & Bots --> SM["AWS Secrets Manager\nfafb/env"]

Tool Tiers

Tools are split so the cloud server only exposes what's safe remotely.

Full reference: docs/tools.md · ECOSYSTEM.md

⚡ Ecosystem Manager (NEW)

Phases 1-6 Complete: Secure, integrated toolkit for managing 129 MCP tools with Discord OAuth, admin approval workflows, and automatic tool synchronization.

Key Features

✅ Phase 1: Discord OAuth2 PKCE flow for user authentication ✅ Phase 2: Auto-extract 129 tools + auto-sync UI on push to main ✅ Phase 3: Tool creation, testing, and admin approval workflow ✅ Phase 4: Auto-generate Gamma presentation decks ✅ Phase 5: GitHub PR-based tool submission with CI tests ✅ Phase 6: Admin UI forms + parameter validation

Create a Tool

Via Web UI:

1. Go to https://ui.mcp.chrismarasco.io/admin/create-tool
2. Fill in tool details (name, description, parameters)
3. Click "Create Tool" → saved to ~/.claude/pending-tools/
4. Test via /admin/pending-tools
5. Admin approves → commits to main → auto-deploys

Via MCP:

fafb repo_create_tool --name "my_tool" --description "Does X" --tier "hosted"
fafb repo_test_tool --tool_name "my_tool" --test_input_json '{}'
fafb repo_approve_tool --tool_name "my_tool"

See ECOSYSTEM.md for complete workflow and API reference.

Quick Start

Connect to the live server

Claude Code CLI:

# HTTP — works in any project
claude mcp add --transport http MCP_CABOOSE https://mcp.chrismarasco.io/mcp

# User scope — available across all projects
claude mcp add --transport http --scope user MCP_CABOOSE https://mcp.chrismarasco.io/mcp

VS Code — add to .vscode/mcp.json:

{
  "servers": {
    "fafb": {
      "type": "http",
      "url": "https://mcp.chrismarasco.io/mcp"
    }
  }
}

Bruno — open the bruno/ folder as a collection.

Run locally (Claude Code on Pi)

cd packages/server && go build -o fafb .

# Interactive setup wizard — writes .env
./fafb --se