Skip to main content
Codex launches the Alphacast MCP server as a local subprocess via npx. You can add it with a single CLI command, or by editing config.toml. The CLI and IDE extension share the same configuration.
codex mcp add alphacast --env ALPHACAST_API_KEY=YOUR_API_KEY -- npx -y @alphacast/mcp
To check configured servers:
codex mcp list

config.toml (manual)

Edit ~/.codex/config.toml for user scope, or create .codex/config.toml at your project root for project scope.
config.toml
[mcp_servers.alphacast]
command = "npx"
args = ["-y", "@alphacast/mcp"]

[mcp_servers.alphacast.env]
ALPHACAST_API_KEY = "YOUR_API_KEY"
Do not commit a real API key to a project-scoped config.toml. Use environment variable forwarding instead:
[mcp_servers.alphacast]
command = "npx"
args = ["-y", "@alphacast/mcp"]
env_vars = ["ALPHACAST_API_KEY"]
This reads ALPHACAST_API_KEY from your local environment at runtime.

Verify

In a Codex session, type /mcp to see active servers. The alphacast server should appear with its 32 tools. Try a prompt:
“Use the alphacast tools to list my repositories.”
If the server fails to start, ensure Node.js 18+ is installed and npx is on your system PATH.