Mcp Spine

Name: Mcp Spine
Author: Donnyb369

@Donnyb369

リポジトリ

Mcp Spine について

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

#proxy #middleware #security #mcp #token-optimization #schema-minification #audit #rate-limiting #windows #python

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

python

トランスポート

stdio

公開者

Donnyb369

投稿者

Donnyb369

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Mcp Spine?

Mcp Spine is a local-first proxy that sits between an MCP client (such as Claude Desktop) and your MCP servers. It adds security, routing, token control, and compliance — handling what goes in, what comes out, and what gets logged — all through a single configuration file.

How to use Mcp Spine?

Install with pip install mcp-spine (add [ml] for semantic routing). Run mcp-spine init for an interactive setup wizard, then start the proxy with mcp-spine serve --config spine.toml. Replace individual MCP server entries in your client configuration with a single Spine entry pointing to the proxy.

Key features of Mcp Spine

Security proxy with rate limiting, secret scrubbing, and path jails
Semantic router using local embeddings (no API calls)
Schema minifier achieving 61% token savings at default level
Human-in-the-loop confirmation for destructive tools
Prompt injection detection in tool responses
Multi-user audit trail with session tagging
Web dashboard for live monitoring and analytics

Use cases of Mcp Spine

Centralize security policies across multiple MCP servers
Reduce token consumption by minifying tool schemas and routing only relevant tools
Enforce daily token budgets per user or server
Audit all tool calls with session tracking for shared deployments
Prevent prompt injection and command injection in agent workflows

FAQ from Mcp Spine

How is Mcp Spine different from running MCP servers directly?

It acts as a middleware proxy that adds security, routing, token control, and audit logging between the client and servers — capabilities not available when connecting tools directly.

What are the runtime requirements?

Python 3.8+ is required. The base install uses only standard library dependencies; optional ML dependencies (pip install mcp-spine[ml]) enable semantic routing.

Where does audit data live?

All audit events, token budgets, and session data are stored in a local SQLite database (default spine_audit.db). No data leaves your machine.

What transport protocols are supported?

stdio (local subprocess servers), SSE (legacy remote servers), and Streamable HTTP (MCP 2025-03-26 spec).

Does semantic routing require external API calls?

No. It uses the local embedding model all-MiniLM-L6-v2 with ChromaDB for tool indexing — all processing stays on your machine.

「その他」の他のコンテンツ

Production-ready MCP integrations for AI applications

Klavis-AI

Klavis AI: MCP integration platforms that let AI agents use tools reliably at any scale

5.8K

Sequential Thinking

modelcontextprotocol

Model Context Protocol Servers

88.2K

🚀 Model Context Protocol (MCP) Curriculum for Beginners

microsoft

This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,

16.7K