IDE Integration Overview

Use the IDE path when you want DecisionOps to be part of the coding flow instead of something you visit only after the work is finished. The IDE integration lets you look up earlier decisions, create a new draft from the task in front of you, validate that draft against organization constraints, and publish a record without leaving your editor for every step.

DecisionOps connects to IDEs through MCP. Every supported platform follows the same high-level pattern:

1. Add the DecisionOps MCP server to your IDE configuration.
2. Trigger any DecisionOps tool from the IDE.
3. Complete the browser-based OAuth consent flow.
4. Retry the same tool call.
5. Use the tools to search, draft, validate, publish, and read decisions.

The current supported platforms are:

• Codex
• Claude Code
• Cursor
• VS Code
• Antigravity

The main difference between the platform guides is where the MCP configuration lives. Codex and Antigravity use user-scoped config, which makes the connection available across repositories. Claude Code, Cursor, and VS Code use project-scoped config, which keeps the MCP setup inside the repository folder.

What You Need First

Before you start, make sure you have:

• access to the DecisionOps organization and project you want to use
• a repository or coding context that maps to the right project
• a supported IDE or coding tool
• permission to edit the MCP config file for that platform

You do not need GitHub sign-in specifically for IDE access. The IDE flow uses DecisionOps OAuth, not GitHub App auth. If you are already signed in to the dashboard, the consent step is usually faster, but it is still a separate authorization step.

What You Can Do From The IDE

Once the connection is working, the DecisionOps MCP tools support a practical authoring workflow:

• do-prepare-decision-gate checks whether the current context should create or update a decision record
• do-search-decisions helps you find earlier decisions before you reinvent an approach
• do-create-decision-draft turns intent and context into a structured draft
• do-validate-decision checks the draft against organization rules and constraints
• do-publish-decision publishes the result using optimistic concurrency
• do-get-decision reads back an existing record when you need to inspect the latest state

This means the IDE path works well for developers who want governance close to implementation, while still keeping the dashboard available for broader review, history, and administration.

Choose Your Platform

Use the guide that matches where you are working:

• connect-from-codex.md
• connect-from-claude-code.md
• connect-from-cursor.md
• connect-from-vscode.md
• connect-from-antigravity.md

Then use the shared workflow pages for the rest of the flow:

• authorize-mcp-access.md
• search-decisions-while-coding.md
• draft-validate-and-publish-from-ide.md
• ide-troubleshooting.md

What Success Looks Like

You know which config file to edit, how the first-run consent flow behaves, and where to go next after the platform is connected. In the dashboard, /integrations/agents should also show the connected client once the first successful authorization is complete.