Connect Codex to Dora and it can read a client request's brief, thread, and files, do the work, and hand it back for the client's review. Questions and approvals stay on the request, where the client already is.

  1. 1

    Add the server

    Add Dora to Codex as an MCP server with the URL https://dora.work/mcp.

  2. 2

    Sign in

    Approve the connection in your browser when Codex asks you to sign in.

  3. 3

    Point it at a request

    Give Codex the request's link and ask: "Work on this request and hand it over for review."

  • The brief and the thread

    Everything the client and your team said on the request, in order, with its files. Codex works from what the client asked for, not your paraphrase of it.

  • The client's world

    Their agreement, brand profile, rules and decisions, and the related files in their library. Codex follows the client's current versions, not last year's.

  • How it was done before

    Similar requests already delivered for the client, with what was handed over each time, so new work matches what they've approved before.

  • A way to ask

    When something's missing, Codex can ask the client in a comment on the request. The client answers in the portal or by email, and the answer lands in the thread.

  • A proper handover

    It submits the work with a note, a preview link, and files. The request moves to In review and the client approves it or asks for changes.

  • Your team's call on scope

    Estimates for work outside the client's agreement are a team-only tool, marked as a change to check with you before making. The client approves or declines it on the request.

  • Give it the request's link and say "Work on this request and hand it over for review." Dora's server gives connected apps its steps for a request: read the context, do the work, then submit it with a note, a preview link, and files. Dora also offers a work_on_request prompt to MCP apps that support prompts, for your team only.

  • One call to get_request_context gives it the request and its full thread, its files, the kind of request and what it needs, the client's rules and decisions, their agreement and brand profile, related items from their library, and similar requests already delivered. That's the same context your team works from in the app.

  • Codex can ask the client for exactly what's missing in a comment on the request. Posting a comment counts as a change, so Codex checks with you first, depending on its approval settings. The client answers in the portal or by email, and the reply lands on the request for Codex, or your team, to pick up.

  • From wherever you deploy previews. Dora doesn't host or deploy your work, so Codex includes the link from your own preview deploy in the handover. The link must start with https://. If there's no preview, it can still hand over a note and files, and the client reviews those instead.

  • The work is posted on the request with its note, preview link, and files, the request moves to In review, and the client team gets one email asking them to review it. If they approve, it's Done. If they ask for changes, it goes back to In progress with their comment, and you can point Codex at it again.

  • Every connection goes through Dora's consent screen. You sign in with a link sent to your email, see which app is asking and where approving sends you back to, and choose Allow or Cancel. The connection then acts as you, with exactly the access you have in Dora and no more. What Codex does in Dora is labeled with its name, and you can disconnect it any time.

  • Every Dora tool tells Codex whether it only reads, and whether a change can't simply be taken back: posting a comment, editing a request, handing over work, sending an estimate, or inviting someone, so Codex can check with you before running them. Reading your briefing, a request, or a client's library never changes anything. When and how often you're asked is set in Codex's own permission settings, not in Dora.

  • No. Dora is priced per client, not per seat or per connection: your first client is free forever, and each client after that is $10 a month. Your own AI working through Dora's MCP has no limit. The one exception is ask_dora, which runs Dora herself and counts against your company's Dora allowance, like a message to her in the app. Codex's own plan is separate.

  • Check the address is exactly https://dora.work/mcp. If Codex says it needs to sign in, run its sign-in again: Dora sends an email link, then shows the consent screen. You need a Dora account first, on a team or as a client; an AI app can't create one for you. If tools you expect are missing, it's usually your role, since clients don't get team tools. Every tool is listed at https://dora.work/docs/mcp.


Add your website and your portal is set up in about a minute.

  • Free for your first client
  • No card needed
  • Set up in a minute
  • Works with Claude and ChatGPT