Skip to content

Daily insider-buy trading plan

Sign up free

Connect InsiderAlpha to Codex CLI

Codex is configured in TOML rather than JSON, and remote servers are the one case its convenience command does not cover: codex mcp add is documented for stdio servers, so an HTTPS server like this one is added by editing config.toml directly. Once the entry exists, Codex has a proper OAuth login subcommand, which is the cleanest of the token options here.

Server URL: https://mcp.insideralpha.ai/mcp. You need an InsiderAlpha account. Sign up free if you do not have one, then follow the steps below.

Setup in Codex

3
  1. Open the config file

    ~/.codex/config.toml for every project, or .codex/config.toml inside a project to scope it there.

  2. Add an mcp_servers entry by hand

    codex mcp add is documented for stdio servers, taking a command to run. A remote HTTPS server is added by writing the table below into config.toml.

  3. Log in, or point at a token

    With auth set to oauth, run codex mcp login insideralpha to complete sign-in. With a Personal Access Token, export it and name the variable in the config instead.

Configuration

Paste one of these into ~/.codex/config.toml or .codex/config.toml.

OAuth login

[mcp_servers.insideralpha]
url = "https://mcp.insideralpha.ai/mcp"
auth = "oauth"

Then run: codex mcp login insideralpha

Personal Access Token from an environment variable

[mcp_servers.insideralpha]
url = "https://mcp.insideralpha.ai/mcp"
bearer_token_env_var = "INSIDERALPHA_MCP_TOKEN"

bearer_token_env_var takes the NAME of the environment variable, not the token itself. Mint the token on your MCP tokens page; it starts with iamcp_ and is shown once.

Codex troubleshooting

3

Failure modes specific to this client, and what is actually going on.

What you seeWhy, and what to do
codex mcp add will not take a URLThat command is for stdio servers, where it expects a command to launch. Remote HTTPS servers go into config.toml by hand.
I put the token itself in bearer_token_env_var and got 401The field holds the name of an environment variable, so Codex sends the literal token string as a variable name and the lookup fails. Export the token under a name and put that name in the config.
A CLI session keeps working after I revoked the tokenToken validation is cached for about a minute. Revocation takes effect within roughly sixty seconds.

Good to know

  • Codex also supports http_headers and env_http_headers for static or environment-sourced headers if you need a form other than a bearer token.
  • If the Redis instance behind our OAuth flow is unavailable, new OAuth sign-ins fail while Personal Access Token connections keep working, because tokens are validated against the backend rather than the OAuth session store.

What the server exposes

19 tools in total: 14 read-only research, market and portfolio tools, plus 5 that act on a connected broker account and are switched off unless you explicitly enable them. The full list, the scopes and the rate limits are the same whichever client you use, so they live in one place: the MCP server reference.

Setting up a different client

Codex setup steps verified against OpenAI Codex documentation: MCP (CLI surface) on 2026-08-09. Codex controls its own interface and can change it without notice, so if a menu name here does not match what you see, trust their documentation over ours and tell us.

InsiderAlpha returns SEC filing data and research output. It is informational and is not investment advice, and nothing it returns is a recommendation to buy or sell any security. You are responsible for every order placed from your own account.

Related