MCP Spine MCP Server

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

Local serverstdioPython

What is the MCP Spine MCP server?

MCP Spine MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Spine directly instead of describing what you should do. 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.

Setting it up

The server ships on PyPI as mcp-spine, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once MCP Spine is connected, these are the calls the assistant has available:

  • Diagnostics — The Diagnostics tool exposed by this server

Configuration and credentials

You will need 2 environment variables: GITHUB_TOKEN, BRAVE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp spine mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Spine's toolset — Diagnostics — is a fair guide to whether it matches your workflow. It is maintained by donnyb369; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Spine's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
DiagnosticsThe Diagnostics tool exposed by this server.

How to install the MCP Spine MCP server

{
  "mcpServers": {
    "spine": {
      "command": "uvx",
      "args": ["mcp-spine"],
      "env": {
        "GITHUB_TOKEN": "your-value",
        "BRAVE_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GITHUB_TOKENCredential the server authenticates with.Yes
BRAVE_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Spine to Diagnostics.

Frequently asked questions

It connects MCP Spine to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Diagnostics) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Spine directly.