Connect meeting notes to Codex via MCP (one-command setup)
Last updated: September 16, 2026
One codex mcp add registers Milago's hosted MCP server for the Codex CLI, the IDE extension and the desktop app at once. The key lives in an environment variable, not in the config file. From then on Codex can search your meetings, read summaries, and pick up tasks from your Action Board — with the decision and the transcript moment that created them.
Setup: three steps
- Generate an API key. In Milago, open Settings → API Keys and create a key with Read + Write scopes. Copy the
mk_live_…value — it is shown once. API keys are available on every plan, including Free. - Register the server. In a terminal, run:
It adds this tocodex mcp add milago --url https://milago.ai/api/mcp --bearer-token-env-var MILAGO_API_KEY~/.codex/config.toml— the file the CLI, the IDE extension and the Codex app all read — so you can also paste it by hand:[mcp_servers.milago] url = "https://milago.ai/api/mcp" bearer_token_env_var = "MILAGO_API_KEY" - Set the key and connect. Put
MILAGO_API_KEY=mk_live_…in your shell profile (setx MILAGO_API_KEY mk_live_…on Windows), open a new terminal, startcodexand type/mcp. Milago is listed with its tools. Try “List my pending Milago tasks.”
The endpoint is Milago's hosted MCP server (Streamable HTTP) at https://milago.ai/api/mcp. Codex sends the variable's value as Authorization: Bearer mk_live_… on every request — the same header-based auth Cursor and CI agents use, so nothing secret is written to disk.
Hand a board task to Codex
Every card on the Milago Action Board has Send to → Codex. Milago queues the run and copies a prompt that carries the task, its priority, the project it is filed under, the meeting it came from and the exact moment in the discussion that created it — the provenance no other board can hand an agent. Paste it into Codex. The prompt asks Codex to call start_task_run first (the card flips to working), post one-line post_task_progress events as it goes, and finish with submit_task_result — with the pull request URL when it opened one — so the card closes itself or lands in your review.
What Codex can do once connected
Codex gets the same 13 Milago tools as every MCP client: search_meetings, ask_milago, get_meeting_summary, search_knowledge, get_pending_tasks, get_sprint_tasks, get_design_feedback, create_task, update_task_status, log_completion, start_task_run, post_task_progress, submit_task_result. In practice that means: search meetings and extracted knowledge, ask a question across every meeting with cited answers, pull a full meeting summary into the session, list pending tasks, read the board, create tasks, update task status, log completed work — and report on a handed-off task as it runs. Full tool descriptions and example prompts are on the Claude integration page — the tool set is identical.
Where the meeting notes come from
Milago is an AI notetaker: send its bot to Zoom, Google Meet, or Microsoft Teams calls — or record locally in the browser, the desktop app, or mobile — and it transcribes the meeting and extracts summaries, tasks, decisions, and knowledge. See the full MCP setup guide for troubleshooting, or pricing for plans.
Frequently asked questions
Which Codex surfaces does this work in?
The Codex CLI, the Codex IDE extension and the Codex desktop app read the same ~/.codex/config.toml, so one codex mcp add registers Milago for all three. Type /mcp inside Codex to see the Milago tools listed.
Why an environment variable instead of pasting the key into config.toml?
Codex reads the bearer token from the variable named by bearer_token_env_var at start-up, so the config file holds no secret and can be checked in or shared. Set MILAGO_API_KEY once in your shell profile (or with setx on Windows) and every Codex surface picks it up.
Can Codex work on a task from my Milago board?
Yes. On the Action Board, choose Send to → Codex on a card: Milago queues the run and copies a prompt that carries the task, the decision behind it and the moment in the meeting that created it. Paste it into Codex; it reports progress back over MCP (start_task_run, post_task_progress, submit_task_result) and the card moves as it works.
Which Milago plans include this?
Every plan, including Free. API keys are generated in Milago under Settings → API Keys; paid plans add recording hours, seats and storage, not API access.
Can I revoke the key?
Yes. In Milago, open Settings → API Keys and revoke it — requests using it get a 401 immediately. Generate a new key and update MILAGO_API_KEY; the config.toml entry does not change.
Is my meeting data used to train AI models?
No. Milago never uses your data for AI training. Data is encrypted in transit with TLS and API keys are hashed with SHA-256; you own your data and can export or delete it anytime.