Skip to main content
Claude Code launches the Alphacast MCP server as a local subprocess via npx. You can add it with a single CLI command, or by editing the project-level .mcp.json file. Run this from any directory inside your project. The server is added at the user scope by default — pass --scope project to share it with collaborators via a checked-in .mcp.json. 
claude mcp add alphacast -e ALPHACAST_API_KEY=YOUR_API_KEY -- npx -y @alphacast/mcp
To remove it later: 
claude mcp remove alphacast
To list configured servers and their status: 
claude mcp list

​
.mcp.json (project-scoped, checked into the repo)

If you want the server available to anyone who clones the project, create or edit .mcp.json at the repo root:
.mcp.json
{
  "mcpServers": {
    "alphacast": {
      "command": "npx",
      "args": ["-y", "@alphacast/mcp"],
      "env": {
        "ALPHACAST_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
Do not commit a real API key to a project-scoped .mcp.json. Use an environment variable reference (e.g. "ALPHACAST_API_KEY": "${ALPHACAST_API_KEY}") and document the variable in your project README.

​
Verify

Open a new Claude Code session and run: 
/mcp
The alphacast server should appear with 32 tools and a green connected status. If it shows red, run claude mcp list to inspect the configured command and environment. Try a prompt that hits a read-only tool to confirm the connection end-to-end:
“Use the alphacast MCP to list my repositories.”