Connect From VS Code
Use this guide when you want to connect DecisionOps to VS Code through MCP. In the current platform catalog, VS Code supports MCP access but not the separate DecisionOps skill flow, so this setup focuses on the MCP server only.
Use this guide when you want to connect DecisionOps to VS Code through MCP. In the current platform catalog, VS Code supports MCP access but not the separate DecisionOps skill flow, so this setup focuses on the MCP server only.
What You Need First
Before you begin, make sure you have:
- VS Code installed
- the correct repository folder open as your workspace
- access to the DecisionOps organization and project for that repository
- permission to edit
{repo_path}/.vscode/mcp.json
The default DecisionOps MCP settings for VS Code are:
- server name:
decision-ops-mcp - server URL:
https://api.aidecisionops.com/mcp
Add The VS Code MCP Config
In the dashboard, go to /integrations/agents and choose VS Code. Select the organization, project, and repository context you want to use, then copy the generated install details.
Create or edit {repo_path}/.vscode/mcp.json in the repository and add the DecisionOps server entry. Because this is a project-scoped file, each repository can point at the context it actually uses in DecisionOps.
If you were expecting a broader VS Code skill integration, that is the main limitation to keep in mind today: the catalog marks VS Code as MCP-supported, but not skill-supported. In practice, that means the MCP setup is the supported path for DecisionOps in VS Code right now.
Authorize And Retry
Invoke a DecisionOps MCP tool from VS Code. The first call should trigger the DecisionOps OAuth handoff in the browser. Complete the login and consent steps, then return to VS Code and retry the same tool call.
Once the retry succeeds, the connection should be usable for the normal DecisionOps workflow: search, draft, validate, publish, and read decisions from inside the editor.
Confirm Success
Open /integrations/agents in the dashboard and confirm that VS Code appears in the connected client list. If it does not appear right away, refresh the page after the first successful tool call.
Troubleshooting
If the tools do not appear in VS Code, confirm that .vscode/mcp.json exists in the workspace folder you actually opened. If consent completed but the client is still missing from the dashboard, retry the same tool call once more to force a successful post-consent request. If you need a skill-style workflow, note that only MCP support is cataloged for VS Code today.
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.
Connect From Antigravity
Use this guide when you want to connect DecisionOps from Antigravity. Like Codex, Antigravity is modeled as a user-scoped MCP integration, but the config path is environment-driven instead of fixed to a single well-known file.