MCP Server

384 MCP tools for your AI editor. One binary. Zero dependencies.

What It Does

stockyard-mcp is a single binary that connects your AI editor to every running Stockyard tool. Feature flags, cron jobs, alerts, caching, cost tracking, guardrails, and 120+ more — all available as native MCP tools in Cursor, Claude Desktop, Windsurf, or Cline.

Ask your editor “What’s my LLM spend this month?” and it calls CostCap. Ask “Create a feature flag called dark-mode at 10% rollout” and it calls SaltLick. The adapter translates MCP tool calls into HTTP API calls to the correct running tool and returns the result.

Install

curl -fsSL https://stockyard.dev/stockyard-mcp/install.sh | sh

Or build from source:

git clone https://github.com/stockyard-dev/Stockyard.git
cd Stockyard && go build -o stockyard-mcp ./cmd/stockyard-mcp/

Usage

# Connect to specific running tools
stockyard-mcp --tools costcap:4100,llmcache:4200

# Auto-discover tools on a port range
stockyard-mcp --scan 4000-7000

# Connect to all tools at default ports
stockyard-mcp --all

# List all 125 known products
stockyard-mcp --list

How It Works

Your AI Editor (Cursor / Claude Desktop / Windsurf / Cline)
    ↓ MCP protocol (JSON-RPC over stdio)
stockyard-mcp (7 MB binary, embedded catalog)
    ↓ HTTP API calls
Running Stockyard tools (costcap:4100, llmcache:4200, ...)

The adapter embeds a catalog of all 125 Stockyard products and their API schemas. When a tool is running, the adapter exposes its endpoints as MCP tools. When the editor calls a tool, the adapter translates the MCP request into an HTTP call to the correct tool instance.

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "stockyard": {
      "command": "stockyard-mcp",
      "args": ["--tools", "costcap:4100,llmcache:4200"]
    }
  }
}
Config location: macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Cursor

Create .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "stockyard": {
      "command": "stockyard-mcp",
      "args": ["--scan", "4000-7000"]
    }
  }
}

Windsurf

{
  "mcpServers": {
    "stockyard": {
      "command": "stockyard-mcp",
      "args": ["--all"]
    }
  }
}

Cline (VS Code)

{
  "mcpServers": {
    "stockyard": {
      "command": "stockyard-mcp",
      "args": ["--all"]
    }
  }
}

Platform MCP (SSE Transport)

The Stockyard platform also exposes an MCP endpoint via SSE for routing LLM requests through the full middleware chain. This is separate from stockyard-mcp — it proxies LLM completions rather than exposing tool APIs.

GET  /mcp/sse       — SSE connection
POST /mcp/message   — JSON-RPC messages

To use the SSE transport in Claude Desktop:

{
  "mcpServers": {
    "stockyard-proxy": {
      "url": "https://your-instance.com/mcp/sse",
      "transport": "sse"
    }
  }
}

All 125 Products

Every Stockyard tool becomes MCP-accessible. Browse the full catalog at stockyard.dev/tools or run stockyard-mcp --list.

Compare Stockyard

vs LiteLLM · vs Helicone · vs Portkey · Pricing · Blog

Explore: Proxy-only mode · Self-hosted proxy · OpenAI-compatible
Why connect AI editors to self-hosted tools

AI-powered editors like Cursor, Windsurf, and Claude Desktop are increasingly capable of calling external tools via MCP. But most MCP servers expose a single service — one server for GitHub, one for Slack, one for Notion. stockyard-mcp takes a different approach: one binary that connects your editor to an entire suite of self-hosted developer tools. Feature flags, cron scheduling, webhook relay, alerting, caching, cost tracking, secrets management, and 120+ more — all discoverable and callable from your editor without leaving your codebase.

The adapter runs locally, connects to your running Stockyard tool instances over HTTP, and translates MCP tool calls into API requests. No cloud dependency. No third-party data sharing. Your tools, your infrastructure, your editor.