Other MCP Clients

Connect VS Code, Zed, Windsurf, and any custom MCP client to the Alphacast MCP server.

The Alphacast MCP server is an npm package (@alphacast/mcp) that runs as a local subprocess via npx. It communicates over stdio. The exact configuration format varies by client, but the values are always the same:

Field	Value
Command	npx
Args	["-y", "@alphacast/mcp"]
Environment	ALPHACAST_API_KEY=YOUR_API_KEY

VS Code (GitHub Copilot Chat / Continue)

VS Code MCP support lives in .vscode/mcp.json for project scope or in user settings for global scope.

.vscode/mcp.json

{
  "servers": {
    "alphacast": {
      "command": "npx",
      "args": ["-y", "@alphacast/mcp"],
      "env": {
        "ALPHACAST_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Reload VS Code after saving the file.

Zed

Zed configures MCP servers in its settings.json under context_servers.

{
  "context_servers": {
    "alphacast": {
      "command": {
        "path": "npx",
        "args": ["-y", "@alphacast/mcp"],
        "env": {
          "ALPHACAST_API_KEY": "YOUR_API_KEY"
        }
      }
    }
  }
}

Windsurf

Windsurf MCP servers are configured in ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "alphacast": {
      "command": "npx",
      "args": ["-y", "@alphacast/mcp"],
      "env": {
        "ALPHACAST_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Custom clients

If you’re building your own MCP client with the official SDKs, spawn the server as a child process (npx -y @alphacast/mcp) with ALPHACAST_API_KEY in the environment, then connect via the SDK’s stdio transport. The server requires no other handshake or registration step.