donnyb369/mcp-spine

Analytics & monitoring

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。原文を見る

12 stars 7 forks 品質 70 トレンド 19MIT

Repository Install

Context Minifier & State Guard — Local-first MCP middleware proxy

概要

Security, routing, token control, and compliance — between your LLM and your tools. MCP Spine is a local-first proxy that sits between Claude Desktop (or any MCP client) and your MCP servers. One config, one entry point, full control over what goes in, what comes out, and what gets logged. 57 tools across 5 servers. One proxy. Zero tokens wasted. You've connected Claude to GitHub, Slack, your database, your filesystem. Now you have 40+ tools loaded, thousands of tokens burned on schemas every turn, no audit trail, no rate limits, and no way to stop the LLM from reading your boss's DMs. MCP gives agents power. Spine gives you control. Runs on Windows, macOS, and Linux. CI tested across all three.

README

以下は原文 README の抜粋です。原文を見る。

MCP Spine

The middleware layer MCP is missing. Security, routing, token control, and compliance — between your LLM and your tools.

MCP Spine is a local-first proxy that sits between Claude Desktop (or any MCP client) and your MCP servers. One config, one entry point, full control over what goes in, what comes out, and what gets logged.

57 tools across 5 servers. One proxy. Zero tokens wasted.

The Problem

You’ve connected Claude to GitHub, Slack, your database, your filesystem. Now you have 40+ tools loaded, thousands of tokens burned on schemas every turn, no audit trail, no rate limits, and no way to stop the LLM from reading your boss’s DMs. MCP gives agents power. Spine gives you control.

What It Does

Layer	What it solves
Security Proxy	Rate limiting, secret scrubbing, path jails, HMAC audit trail
Semantic Router	Only relevant tools reach the LLM — local embeddings, no API calls
Schema Minifier	61% token savings by stripping unnecessary schema fields
State Guard	SHA-256 file pins prevent the LLM from editing stale versions
Token Budget	Daily limits with warn/block enforcement and persistent tracking
Plugin System	Custom middleware hooks — filter, transform, block per tool
HITL Confirmation	Destructive tools pause for human approval before executing
Injection Detection	Scans tool responses for prompt injection before they reach the LLM
Multi-User Audit	Session-tagged audit trail for shared deployments
Tool Caching	LRU cache for read-only tools — skip redundant downstream calls
Webhook Alerts	Slack/Discord/JSON notifications on security events and budget warnings
Web Dashboard	Browser-based monitoring with live stats, latency tracking, request log

Demo

Runs on Windows, macOS, and Linux. CI tested across all three.

Web Dashboard

mcp-spine web --db spine_audit.db

Install

pip install mcp-spine

# With semantic routing (optional)
pip install mcp-spine[ml]

Quick Start

# Interactive setup wizard — detects your servers, asks about features
mcp-spine init

# Or quick default config
mcp-spine init --quick

# Check everything works
mcp-spine doctor --config spine.toml

# Start the proxy
mcp-spine serve --config spine.toml

# Open the web dashboard
mcp-spine web --db spine_audit.db

# Export analytics
mcp-spine export --format csv --hours 24 --output report.csv

Claude Desktop Integration

Replace all your individual MCP server entries with a single Spine entry:

{
  "mcpServers": {
    "spine": {
      "command": "python",

GitHub で README 全文を見る

インストール

This server does not publish a one-line install command.

Open the repository installation guide MCP 初心者？mcpskill.org のガイドから始めましょう →

設定

{
  "mcpServers": {
    "spine": {
      "command": "python",
      "args": ["-m", "spine.cli", "serve", "--config", "/path/to/spine.toml"],
      "cwd": "/path/to/mcp-spine"
    }
  }
}