MCP Servers

Connect external tools through Model Context Protocol.

AlphaBase can connect to MCP servers for external tools and context providers.

Manage MCP Servers

Use CLI:

alphabase mcp

Or manage through runtime routes/UI controls depending on your client surface.

Config Schema

MCP servers are defined under the mcp config key, in two forms:

{
  "mcp": {
    "local-example": {
      "type": "local",
      "command": ["npx", "-y", "@some/mcp-server"],
      "environment": {
        "API_KEY": "{env:SOME_API_KEY}",
      },
    },
    "remote-example": {
      "type": "remote",
      "url": "https://mcp.example.com/mcp",
      "headers": {
        "Authorization": "Bearer {env:REMOTE_MCP_TOKEN}",
      },
    },
  },
}

type: "local" — spawns a subprocess; command is an array containing the executable followed by its arguments, with optional environment, enabled, and timeout.
type: "remote" — tries Streamable HTTP and then SSE; supports url, optional headers, optional oauth, enabled, and timeout.

See Config.

Typical Flow

register MCP server config
enable/disable per environment
grant permissions for MCP tools
verify server health and tool discovery

Security

treat MCP servers as code execution/data access boundaries
scope credentials minimally
review tool permissions (ask, allow, deny) for each MCP namespace

See Permissions and Tools.