Connect Codex to Alpaca
Set up in minutes
Choose where it runs
On your computer through your own Codex, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in Alpaca
A preset of real Alpaca operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Alpaca
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your Codex first calls in. Codex connects when a session starts — run codex, or restart a running one (in the Codex app, Restart).
Run this in your terminal. The Codex app shares its config, so it gets the server too
<your-link> is your personal server URL — setup mints it for you.
Tools Codex gets
Alpaca
25 toolsOne activity page; pass the last activity ID as page_token for the next.
One page, bounded by limit; use after/until or the order ID cursors to continue.
Submit a single-leg order. Acceptance does not mean a fill; do not blindly retry.
Replacement request; inspect the returned order status for completion.
Request cancellation; a 204 acknowledges the request, not final cancellation.
Submit an order to close all or part of one position; filling is asynchronous.
About Codex
Frequently asked questions
More ways to connect
Open your Codex agent in one click.
NoClick runs Codex for you with Alpaca wired in as tools. Connect your account and run.