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.
@Donnyb369
Basic information
Context Minifier & State Guard — Local-first MCP middleware proxy
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"spine": {
"command": "python",
"args": [
"-m",
"spine.cli",
"serve",
"--config",
"/path/to/spine.toml"
],
"cwd": "/path/to/mcp-spine"
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
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.
Python 3.8+ is required. The base install uses only standard library dependencies; optional ML dependencies (`pip install mcp-spine[ml]`) enable semantic routing.
All audit events, token budgets, and session data are stored in a local SQLite database (default `spine_audit.db`). No data leaves your machine.
stdio (local subprocess servers), SSE (legacy remote servers), and Streamable HTTP (MCP 2025-03-26 spec).
No. It uses the local embedding model `all-MiniLM-L6-v2` with ChromaDB for tool indexing — all processing stays on your machine.
🔥 MaxKB is an open-source platform for building enterprise-grade agents. 强大易用的开源企业级智能体平台。
PickFu MCP is a Model Context Protocol (MCP) server that connects AI assistants, developers, marketers, product managers, and AI agents to PickFu's consumer research platform. It enables users to create surveys, conduct
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.

Model Context Protocol Servers
Comments