MCP servers

NeuBird Desktop supports the Model Context Protocol (MCP) for connecting external tools. MCP servers extend the AI agent with additional capabilities beyond the built-in telemetry tools.

Managing MCP servers

Use the neubird mcp command to manage your MCP server configuration:

# List configured servers
neubird mcp list

# Add a stdio server (command + args)
neubird mcp add my-server python -m my_mcp_server

# Add an HTTP server (auto-detected from URL)
neubird mcp add my-server http://localhost:3000

# Add with environment variables
neubird mcp add my-server npx -y @my-org/mcp-tool -e API_KEY=your-key

# Add with custom HTTP headers
neubird mcp add my-server http://localhost:3000 --header "Authorization: Bearer token"

# Remove a server
neubird mcp remove my-server

Configuration file

MCP servers are stored in ~/.config/neubird/mcp_config.json:

{
  "mcpServers": {
    "my-server": {
      "command": "python",
      "args": ["-m", "my_mcp_server"],
      "env": {}
    }
  }
}

Transports

Stdio (default) — the server runs as a subprocess, communicating via stdin/stdout:

{
  "mcpServers": {
    "my-tool": {
      "command": "npx",
      "args": ["-y", "@my-org/mcp-tool"],
      "env": {
        "API_KEY": "your-key"
      }
    }
  }
}

HTTP — the server runs as an HTTP service (auto-detected when a URL is provided):

{
  "mcpServers": {
    "remote-tool": {
      "url": "http://localhost:3000",
      "headers": {
        "Authorization": "Bearer token"
      }
    }
  }
}

Checking status

Use the /mcp slash command to see which MCP servers are connected and what tools they provide:

> /mcp

Tools from connected MCP servers appear alongside NeuBird’s built-in tools and are available to the AI agent during investigations.