In ~/.codex/config.toml add:
[mcp_servers.annsa]
url = "https://app.annsa.ai/mcp"
auth = "oauth"
Then run:
codex mcp login annsa
01Add the server to config.toml
02Authenticate
The first use opens a browser on Annsa's consent screen — approve once and the six tools appear. There is no API key to paste and no token file to manage; access is your Annsa login, scoped to your workspace.
03The six tools
| Tool | What it does |
|---|---|
annsa.priorities | Ranked priorities with scores, volume, trend and shipping-history flags |
annsa.spec | Full spec for any priority, plus related context from past ships |
annsa.act | Build, ship, share, assign, correct, park, submit feedback or a transcript |
annsa.ask | Search feedback, priorities, specs and help articles |
annsa.surveys | How your in-product surveys are performing — each one with its instrument and results |
annsa.help | How Annsa itself works — product and how-to questions |
04Three things to ask first
"What are my top priorities?" · "Pull the spec for the export bug and implement it" · "Mark priority #2 shipped"
05Re-authenticating
Run codex mcp login annsa again — the browser reopens Annsa's consent screen.
06When it doesn't connect
Server not listed: check the [mcp_servers.annsa] table name is exact and the file is ~/.codex/config.toml.
Auth loop: confirm auth = "oauth" is present — without it Codex expects a static key that doesn't exist.
"No priorities": import some feedback first.
07How do I add an MCP server to Codex?
Add a [mcp_servers.<name>] table to ~/.codex/config.toml with the server's url, set auth = "oauth" for OAuth servers, then run codex mcp login <name>. Codex opens a browser for consent and the server's tools appear in the session.
08Does Codex support OAuth MCP servers?
Yes — set auth = "oauth" on the server entry in config.toml and authenticate with codex mcp login <name>. The token is managed by Codex; there is no key to paste into the config file.