slop-mcp

Install many MCPs without killing your context.

slop-mcp is an MCP orchestrator that lets you connect dozens of MCP servers while exposing only 8 meta-tools to your agent. No more context window bloat from loading hundreds of tool definitions upfront.

Without slop-mcp:  50 MCPs × 20 tools = 1000 tool definitions in context
With slop-mcp:     50 MCPs × 20 tools = 8 tool definitions in context

Documentation

• Quick Start Guide - Get running in 5 minutes

• Full Documentation - Complete guides and reference

• KDL Configuration - Configuration reference

• CLI Reference - Command-line options

Related MCP server: mcpcute

Event Monitoring

slop-mcp integrates with Claude Code's Monitor tool to stream events from any source — git hooks, build tools, CI pipelines, file watchers, or MCP servers.

# Start watching for events (runs until killed)
slop-mcp monitor &

# Send events from anywhere — shell scripts, git hooks, CI, cron
slop-mcp message "commit a1b2c3f: fix auth token refresh"
slop-mcp message "build failed: src/auth.ts(42): TypeError"
slop-mcp message "tests: 43 passed in 1.2s"
slop-mcp message "deploy v0.14.0 → staging (healthy)"

# Or poll MCPs with a SLOP script
slop-mcp monitor watch-deploy.slop

Use with Claude Code:

Monitor({
  command: "slop-mcp monitor",
  description: "build events",
  persistent: true
})

See the Monitoring Guide for git hook templates, build wrappers, and SLOP polling scripts.

Caveman Your MCPs

Third-party MCPs are written for everybody. They ship 400-token marketing-prose descriptions, deprecation caveats, twelve optional parameters you'll never set, and SDK history nobody asked for. Multiply across a dozen MCPs and that's your whole context budget — burned before the first user turn.

slop-mcp lets you rewrite any MCP's metadata to match what your project actually needs:

Before:  generate_image  →  420-token description, 14 params, 6 enums
After:   generate_image  →   30-token description, "use defaults" hints
Custom:  thumbnail       →   12-token description, 1 param (prompt)

Three progression levels:

1. Caveman the descriptions — replace verbose vendor prose with terse agent-friendly text. Original tool unchanged, agent sees only your version.

2. Document hardcoded values — for params your project never varies, the override description says "always pass X" instead of explaining the full enum.

3. Wrap with a custom SLOP tool — define a brand-new tool with a minimal schema (e.g. just prompt) that calls the underlying MCP with all the boilerplate baked in.

Customizations live at user, project, or local scope and can be exported as portable JSON packs and committed to git — your team gets the same compressed interface on clone.

See the Customization Guide for the full image-MCP walkthrough and the customize_tools reference.

The Problem

As described in Anthropic's article Code Execution with MCP, current MCP implementations face two critical challenges:

1. Context Window Overload: When agents connect to many tools, loading all tool definitions upfront consumes excessive tokens. With thousands of connected tools, agents must process hundreds of thousands of tokens before even reading user requests.

2. Intermediate Result Duplication: Tool outputs repeatedly flow through the model's context. Transferring large documents between services forces the same data through the model between operations, potentially doubling token consumption.

The article proposes code execution within MCP as a solution—letting agents discover tools progressively and process data within the execution environment rather than shuttling everything through context.

How slop-mcp Addresses These Issues

slop-mcp takes a different but complementary approach: instead of code execution, it provides an orchestration layer that aggregates multiple MCP servers while maintaining context efficiency.

Progressive Tool Discovery

Rather than loading all tool definitions upfront, slop-mcp exposes just 8 meta-tools:

This means an agent connecting to slop-mcp sees 8 tool definitions regardless of how many MCPs are connected or how many tools they expose. The agent discovers tools on-demand via search_tools and executes them via execute_tool.

Lazy Connection & Async Startup

MCP servers connect asynchronously in the background:

Server starts → Immediately ready to serve
                ↓ (background)
                MCP #1 connecting...
                MCP #2 connecting...
                MCP #N connecting...

The server doesn't block waiting for all MCPs to connect. Tools become available progressively as their MCPs come online.

In-Environment Script Execution

The run_slop tool allows executing structured scripts that can:

• Call multiple tools across different MCPs

• Process intermediate results without sending them back through the model

• Chain operations efficiently

This keeps large intermediate data within the execution environment, addressing the token duplication problem.

Efficient Tool Index

Tools are indexed locally when MCPs connect:

• Fuzzy search by name or description

• Filter by MCP name

• No network calls during search

• Thread-safe concurrent access

Architecture

┌─────────────────────────────────────────────────────┐
│              slop-mcp Server                        │
│  ┌───────────────────────────────────────────────┐  │
│  │  8 Meta-Tools (constant context cost)         │  │
│  │  • search_tools    • execute_tool             │  │
│  │  • get_metadata    • run_slop                 │  │
│  │  • manage_mcps     • auth_mcp                 │  │
│  │  • slop_reference  • slop_help                │  │
│  └───────────────────────────────────────────────┘  │
│                          │                          │
│         ┌────────────────┼────────────────┐         │
│         ▼                ▼                ▼         │
│  ┌────────────┐  ┌────────────┐  ┌────────────┐    │
│  │  Registry  │  │ Tool Index │  │   Auth     │    │
│  │  (async)   │  │  (local)   │  │  (OAuth)   │    │
│  └─────┬──────┘  └────────────┘  └────────────┘    │
└────────┼────────────────────────────────────────────┘
         │
    ┌────┼────┬─────────────┐
    ▼    ▼    ▼             ▼
┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐
│MCP #1│ │MCP #2│ │MCP #3│ │MCP #N│
│stdio │ │ SSE  │ │ HTTP │ │ ...  │
└──────┘ └──────┘ └──────┘ └──────┘

Configuration

slop-mcp uses KDL configuration with three-tier scoping:

Example configuration:

mcp "filesystem" {
    command "npx" "-y" "@anthropic/mcp-filesystem"
    args "/path/to/allowed/dir"
}

mcp "github" {
    transport "sse"
    url "https://mcp.github.com/sse"
    // OAuth handled automatically via auth_mcp tool
}

Import existing configurations:

import "claude-desktop"  // Import from Claude Desktop config
import "claude-code"     // Import from Claude Code settings

Quick Start

npm

npx @standardbeagle/slop-mcp

PyPI

uvx slop-mcp

Or install globally:

# npm
npm install -g @standardbeagle/slop-mcp

# pip
pip install slop-mcp

From Source

go install github.com/standardbeagle/slop-mcp/cmd/slop-mcp@latest

Usage

As an MCP Server (stdio)

slop-mcp serve

With HTTP/SSE Transport

slop-mcp serve --port 8080

Claude Desktop Configuration

Add to your Claude Desktop config:

{
  "mcpServers": {
    "slop": {
      "command": "slop-mcp",
      "args": ["serve"]
    }
  }
}

Comparison with Code Execution Approach

Both approaches solve the same core problems. Code execution offers maximum flexibility but requires sandboxing infrastructure. slop-mcp provides a simpler deployment model while still achieving significant context efficiency gains.

Related Projects

• standardbeagle-tools - Claude Code plugin for slop-mcp integration

License

MIT