Connect From Codex
Use this guide when you want to connect DecisionOps to Codex. Codex uses a user-level MCP configuration, so one setup can work across multiple repositories as long as you choose the right organization, project, and repository context when you install or update the entry.
Use this guide when you want to connect DecisionOps to Codex. Codex uses a user-level MCP configuration, so one setup can work across multiple repositories as long as you choose the right organization, project, and repository context when you install or update the entry.
What You Need First
Make sure you have:
- Codex installed and working locally
- access to the DecisionOps organization and project you want to use
- permission to edit
~/.codex/config.toml
In the current platform catalog, the default DecisionOps server for Codex is:
- server name:
decision-ops-mcp - server URL:
https://api.aidecisionops.com/mcp
Set Up The MCP Entry
Open DecisionOps in the browser and go to /integrations/agents. Choose Codex, then select the organization, project, and repository context you want the install details to represent. This page is the safest place to start because it generates the values for the current workspace instead of relying on memory or copied snippets from another repository.
Add or verify the MCP server entry in ~/.codex/config.toml. The exact surrounding structure can vary with your local Codex setup, but the entry should point to the DecisionOps MCP server name and URL shown above. If you already have an older DecisionOps entry, update it rather than keeping two different server definitions.
Because Codex uses a user-level config file, be careful when you switch between workspaces. A stale organization, project, or repository reference can make the connection succeed technically while publishing into the wrong context.
Trigger Authorization
After saving the config, invoke any DecisionOps MCP tool in Codex. The first tool call normally triggers an interactive login and consent handoff. Your browser opens to DecisionOps, where you may need to sign in, confirm the organization you are authorizing, and allow the MCP client to act on your behalf.
When the consent flow finishes, return to Codex and retry the exact same tool call. The first call establishes the auth challenge; the retry is what confirms the client can now use the granted token.
Confirm The Connection
Go back to /integrations/agents in the dashboard and confirm that Codex appears in the connected clients list. If the connection is active, you can continue with:
authorize-mcp-access.mdfor more detail on the consent flowsearch-decisions-while-coding.mdto reuse prior decisionsdraft-validate-and-publish-from-ide.mdto create records from Codex
Troubleshooting
If Codex does not discover the server, verify that you edited ~/.codex/config.toml and not a different project-level file. If you keep seeing repeated auth prompts, complete consent in the browser and then retry the same tool call instead of moving straight to a new one. If tool calls work but target the wrong workspace, regenerate the install details from /integrations/agents and update the organization, project, or repository values in your config.
Installing MCP
Get oriented on the MCP setup flow before choosing your editor-specific integration guide.
Connect From Cursor
Use this guide when you want to run DecisionOps from Cursor. Cursor stores MCP settings in the repository under `.cursor/mcp.json`, so the connection follows the project rather than your whole machine.