Skip to main content The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery

Codex MCP servers

Turn Codex into an enterprise agent

Let your employees delegate real work to Codex across all their apps, under their own identity and permissions.

DrataGPLocalyzeFlipMindtoolsScreenloop

Get Codex to work.
Not just chat.

One connection to StackOne, and Codex gets scoped access to every app your employees use, to act on their behalf.

Connect

Make every system AI-ready

Give your AI access to 450+ managed MCP servers and 28,000+ tested tools. No auth code to write, no API maintenance.

Secure

Keep AI under control

Enforce identity-based access, screen every response for prompt injection, and audit every action.

Optimize

Trust what AI delivers

Keep your agent sharp with lean tool loading, boost reliability with the Falcon execution engine, and enhance its context with pre-synced data.

Roll out MCP tools to every Codex user.
Set up and onboarding in minutes.

One-time setup for IT. Self-serve for everyone else.

IT Admin

One-time setup, no per-user wiring.

The URL carries no access on its own, so it is safe to publish in an internal wiki or commit with your dotfiles. There is no OAuth app to register and no client secret to hand out. Each person authorizes their own accounts with the login command. Codex setup guide →

Which MCP server will you
connect Codex to?

Connect to the StackOne MCP gateway once and give your employees' agents instant access to 450+ pre-built SaaS connectors and 28,000+ MCP tools.

Need another connector? Build one with the AI Connector Builder

What will your employees
delegate to Codex?

From HR and recruiting to sales and support, Codex completes work across any app you connect.

HR & People Ops

> List this month's Workday work anniversaries and draft a personalized celebration message for each.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify
Recruiting

> Compare Greenhouse interview feedback across stages and flag candidates trending toward an offer.

JobAdderVincereSmartRecruitersAshbyManatalFactorialHiBobSAP SuccessFactors
Sales & CRM

> Analyze Salesforce deals stuck 30+ days and draft a re-engagement email for each owner.

SalesforceKeapZoho CRMPipedriveFreshsalesJustCallPardotAircall
Support

> Cluster yesterday's Zendesk tickets by theme and surface the top 3 trending issues.

IntercomSurveyMonkeyFreshserviceServiceNowFreshdeskGorgiasDiscourseDixa

Not everyone on Codex?
Your integration layer stays the same.

The same setup works across Coding agents like Gemini CLI, Claude Code, and every other MCP client.

Explore MCP clients

Frequently Asked Questions

You connect Codex to StackOne over MCP with two commands: codex mcp add stackone --url https://mcp.stackone.com/mcp registers the server, then codex mcp login stackone opens your browser to authorize — sign in, pick your project, choose accounts and actions. Same entry can go straight into ~/.codex/config.toml. Setup guide.
Codex stores the StackOne MCP server config in ~/.codex/config.toml, and codex mcp add writes it for you. The file is TOML, so the entry is a [mcp_servers.stackone] table with a single url key. It's a plain file, so IT can commit it with your dotfiles — it holds only the gateway address, never credentials.
You can connect Codex to StackOne without the browser consent step by using a session token instead of the login command. Generate one from the Connectors page in your StackOne dashboard ("Use in Agent"), then point [mcp_servers.stackone] at https://api.stackone.com/mcp?token={session_token}. Treat that URL like a credential, not the plain gateway address — it does not belong in a committed dotfile.
You don't configure each app in StackOne yourself. IT connects the apps and sets the action ceiling for your project. Running codex mcp login stackone sends you to a consent screen where you pick which of those accounts and actions to use, narrowing further if you want. Rerun the same command to change it.
Once connected, Codex can run whatever actions you granted, across 450+ live connectors and 28,000+ tested actions — CRM, HRIS, ATS, ticketing, finance, and more. Tools go live once you authorize; ask Codex what StackOne tools are available to see the list. Browse the actions in the directory above.
Your app credentials — Stripe, Salesforce, and the rest — live server-side in StackOne and never reach Codex or your machine. The gateway address in config.toml carries no access on its own, so it's safe to commit with your dotfiles. Setup asks for no client ID or secret; each token is scoped to what you picked.
IT can roll out the StackOne MCP connector to a whole team in one pass: connect the apps once, and distribute a single config.toml entry instead of briefing people individually. Each person still runs the login command, picks their own accounts and actions, and authorizes — so nobody exceeds the ceiling IT set.
Skip connecting Codex to StackOne when any of these is true:
  • An existing first-party MCP server already covers your apps
  • You use only a handful of actions across a few apps
  • You don't need multi-tenancy or per-action scoping
  • Prompt injection isn't a concern
  • Nobody can complete a browser consent step and a session token isn't an option either — a CI job, for instance

Connect All Your Apps to Codex.

One URL, 450+ pre-built SaaS connectors. Set up in minutes.