Skip to main content

Running SignalPilot next to other MCP servers

This page is about the Claude Code side: running SignalPilot alongside other MCP servers such as filesystem, GitHub, or a browser in the same session. Each server keeps its own tools, and SignalPilot's governance applies to its tools no matter what else is connected.

Looking for the other direction, adding outside services such as Linear or Notion into SignalPilot's own chat? That is Add MCP servers to chat.

Example .mcp.json​

A project using SignalPilot plus a filesystem server and a GitHub server:

example .mcp.json
{
  "mcpServers": {
    "signalpilot": {
      "type": "http",
      "url": "https://gateway.signalpilot.ai/mcp",
      "headers": {
        "x-api-key": "sp_your_key_here"
      }
    },
    "filesystem": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/project"]
    },
    "github": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_your_token"
      }
    }
  }
}

For a self-hosted gateway, replace the URL with http://localhost:3300/mcp.

In Claude Code you can also add servers one at a time and they combine:

add servers individually
$ claude mcp add --transport http signalpilot https://gateway.signalpilot.ai/mcp \
  --header "x-api-key: sp_your_key_here"
$ claude mcp add --transport stdio filesystem npx -y @modelcontextprotocol/server-filesystem /path/to/project

Tool name conflicts​

Each MCP server declares its tools independently. If two servers expose a tool with the same name, Claude Code uses the server name as a prefix to tell them apart, so SignalPilot's tools appear as signalpilot__query_database and so on in multi-server sessions.

SignalPilot's tool names are deliberately specific (query_database, list_tables, dbt_error_parser) and are unlikely to collide with general-purpose servers.

Steering Claude toward SignalPilot​

Claude Code shows the model every available tool and lets it choose. To make sure data tasks go through SignalPilot rather than another server, say so in your CLAUDE.md:

claude.md example
For any database or dbt task, use the SignalPilot MCP tools (signalpilot server).
Always call list_database_connections before querying to confirm the right connection is active.

See CLAUDE.md recipes for more templates.

Turning off individual tools​

If a specific SignalPilot tool gets in the way, or you want to keep Claude's tool list short, you can turn individual tools off in Claude Code's MCP settings. Other tools from the same server are unaffected.

Checking health across servers​

Use SignalPilot's connection_health tool to confirm database connectivity on its own. Each server's health is independent, so a problem with one server does not tell you anything about the others.