Codex connects to MCP servers over HTTP, so your Dopia workspace is a URL and an OAuth sign-in away. Once it is in, Codex can look things up, write records back through the same identity resolution the product uses, and leave a finished piece of work behind as a page you can send to someone who has no account.
One command. Nothing to install on our side, and no API key to paste anywhere.
codex mcp add dopia --url https://mcp.dopia.ai/mcpCodex opens the browser and hands the result back on its own. You are signing in to your own workspace — Codex never sees a password.
codex mcp login dopiaIf you would rather keep configuration in one file, the same thing in ~/.codex/config.toml. Sign in afterwards the same way.
[mcp_servers.dopia]url = "https://mcp.dopia.ai/mcp"auth = "oauth"The browser page asks for three things in plain words. It is the same page for every client, and you can take any of it back from Settings afterwards.
crm:readLook up companies, contacts and deals in your workspace.
crm:writeCreate and update records — through the same identity resolution the product uses, so nothing quietly duplicates.
artifacts:writeSave a finished piece of work as a page with its own URL. It can create new ones; it cannot read or change the ones you already have.
No commands to learn. The workspace is simply there, and anything the agent writes stays after the conversation is gone.
One URL, scopes you approve in the browser, and a workspace that keeps what your agents find instead of losing it with the conversation.
MCP over streamable HTTP · OAuth · revoke any time