MCP and direct API integration paths for AI agents
Compare the direct API with the verified MCP path for supported AI tools. Public release status, owner authorization, and runtime availability govern use.
- 01Developer infrastructure is live through MCP and the API, and the trading app launches September 17, 2026.
- 02MCP can connect Felix to supported Claude, Cursor, and Codex clients without requiring an application build.
- 03The verified MCP path is available for supported agent tools.
- 04The API gives developers programmatic control to build an agent.
- 05Both surfaces use the same account, non-custodial controls, venue routes, and limits.
There is no single right integration path for an AI agent. Felix developer infrastructure includes verified agent tooling and the direct API using the same account model, venue routes, and limits.
Browser chat: coming next
The trading app launches September 17. Developer infrastructure is already live through the public MCP package and direct API.
Live Felix infrastructure covers a verified MCP package for supported agent tools and the direct API for custom applications. The trading app launches September 17.
1. MCP: trade from the tools you already use
Operators working in a supported Claude, Cursor, or Codex client can connect Felix over the Model Context Protocol with the public package.
# Choose codex, claude, or cursor for your MCP client
npx -y --package felix-mcp@2.0.110 felix-keys onboard --accept-terms --client codexThis path is intended for people who want an agent tool connection without building a whole application. See the MCP trading architecture.
2. The API: full control for your own agent
Developers building an application can use the direct API. It provides a normalized instrument format, dollar sizing, and endpoints for quotes, orders, positions, PnL, funding, and emergency controls. A manage-scope parent key can create isolated child accounts programmatically.
POST /v1/orders {"instrument":"BTC","side":"buy","size_usd":50}
GET /v1/positions
GET /v1/pnl
POST /v1/panicThis is the foundation the MCP surface uses. Everything the MCP can do, the API can do, plus everything you design on top. See How to give an AI agent a trading account.
Which one should you use?
- Already work in a supported MCP client? Use the verified MCP path.
- Building an agent or an app? Use the direct API for programmatic control.
Both surfaces use the same venue routes and guardrails, so the choice is about how much you want to build. Whichever you pick, execution begins only after owner authorization and remains bounded by owner-authorized limits. See How to run an AI trading agent with real-money controls.
Frequently asked questions
Felix developer infrastructure is live with a verified MCP package for supported clients and the direct API for custom applications. The trading app launches September 17, 2026.
Use the public MCP package from a supported client today. The Felix trading app launches September 17, 2026.
MCP embeds Felix tools in an AI assistant, while the API gives a developer full programmatic control. Both use the same account, venue routes, and limits.
Both paths can submit real-money actions with separate owner authorization. The same scoped permissions and owner-signed limits apply.
Sources and verification
Product claims in this article were checked against these first-party references. Runtime status remains authoritative for current availability.
- Felix documentationfirst party
- Felix machine-readable referencefirst party
- Felix runtime statuslive status
Build with Felix now.
Felix infrastructure is live through MCP and the API. The full trading app launches September 17.
Five market types, one normalized interface, dollar sizing, and runtime status for current availability.
After installation and owner authorization, MCP can expose Felix tools in supported AI clients. Venue truth determines whether an order is accepted or filled.