Skip to main content
Codex has a built-in MCP client. Add AIsa as a remote MCP server, sign in once, and Codex can discover and call AIsa capabilities across web research, finance, social, SEO, sales, and more. AIsa MCP server:

​
Prerequisites

Before you start, make sure you have:
  • An AIsa account (console.aisa.one). You sign in through the browser.
  • A terminal on macOS, Linux, or Windows WSL2

​
1. Install Codex

Or with Homebrew:
Verify the installation:

​
2. Add the AIsa MCP server

Codex detects that AIsa uses OAuth and opens your browser. Sign in to AIsa and approve access; no key is copied. On a machine without a browser, run codex mcp login aisa --no-browser and open the printed URL elsewhere.
For headless environments, export your AIsa key and tell Codex which variable holds it. Codex reads it at runtime, so the key never lands in config.toml:

​
3. Verify

aisa should be listed as enabled, with OAuth (or Bearer token) in the Auth column. Start a new Codex session to load the tools; inside Codex, /mcp shows the connected servers.

​
4. Use AIsa capabilities

Codex now has the AIsa tools. search, list_categories, get_details, batch_get_schema, and batch_quote (prices exact calls without running them) are free; use and batch_use run calls and are billed per call. Try:

​
Optional: run Codex on AIsa models

Codex can also use AIsa as its model provider. This needs an AIsa API key (console.aisa.one/api-keys) exported as AISA_API_KEY. Add this to ~/.codex/config.toml:
  • env_key tells Codex which environment variable holds your key.
  • Codex only supports wire_api = "responses", so pick a model that lists POST /v1/responses in the catalog, such as gpt-5.5, gpt-5.4, or gpt-5.3-codex.

​
Quick reference

​
Troubleshooting

Use AIsa in Claude

Add AIsa as a custom connector in Claude.

Connect via MCP

MCP setup for other clients.

Model Catalog

Browse models that support the Responses API.