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.
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.
What You Need First
Make sure you have:
- Cursor installed
- the correct repository folder open in Cursor
- access to the matching DecisionOps organization and project
- permission to create or edit
{repo_path}/.cursor/mcp.json
The current default DecisionOps MCP settings for Cursor are:
- server name:
decision-ops-mcp - server URL:
https://api.aidecisionops.com/mcp
Configure Cursor
Open /integrations/agents in the DecisionOps dashboard and choose Cursor. Select the organization, project, and repository context you want this workspace to use, then copy the generated install details.
In the repository, open {repo_path}/.cursor/mcp.json and add or verify the DecisionOps server entry. If the .cursor directory does not exist yet, create it first. The most common setup issue here is editing the right file in the wrong checkout, so take a moment to confirm that the folder open in Cursor is the same repository you selected in the dashboard.
Trigger And Finish Authorization
Run any DecisionOps MCP tool from Cursor. On first use, Cursor should trigger an interactive browser handoff to DecisionOps. Complete sign-in if needed, review the requested access, and approve the grant.
After consent finishes, go back to Cursor and rerun the same tool call. Once that retry succeeds, the connection is ready for normal use.
Verify In The Dashboard
Open /integrations/agents again and confirm that Cursor now appears as a connected client. That page is also where you can review older grants or remove stale ones if the repository or workspace context changed.
Troubleshooting
If Cursor cannot find the config, confirm that .cursor/mcp.json exists inside the active repository. If the browser consent window opens but the flow never completes, finish the authorization in the browser before retrying the tool in Cursor. If the connection appears healthy but results come from the wrong project, regenerate the install details from the dashboard and replace the old context values.
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.
Connect From Claude Code
Use this guide when you want DecisionOps inside Claude Code. Claude Code uses a project-scoped MCP file, so the configuration belongs in the repository you are actively working in.