IDE Troubleshooting
Use this page when the platform-specific setup looks right but DecisionOps still is not behaving correctly in your IDE. Most problems fall into one of five buckets: the IDE cannot discover the MCP server, the auth flow repeats, the grant exists but calls still fail, the workspace context is wrong, or the user has less permission than expected.
Use this page when the platform-specific setup looks right but DecisionOps still is not behaving correctly in your IDE. Most problems fall into one of five buckets: the IDE cannot discover the MCP server, the auth flow repeats, the grant exists but calls still fail, the workspace context is wrong, or the user has less permission than expected.
Check In This Order
When something is off, work through these checks in order:
- Verify the correct config file for your platform.
- Verify the server name and URL.
- Trigger one DecisionOps tool call and complete consent.
- Confirm the grant appears on
/integrations/agents. - Recheck organization, project, and repository context.
- Review role and permission issues.
Following this sequence usually separates config problems from auth problems very quickly.
The IDE Does Not Discover The MCP Server
If the tool never appears in the IDE, the most common cause is that the config file is in the wrong location for that platform:
- Codex:
~/.codex/config.toml - Claude Code:
{repo_path}/.mcp.json - Cursor:
{repo_path}/.cursor/mcp.json - VS Code:
{repo_path}/.vscode/mcp.json - Antigravity: the file resolved by
ANTIGRAVITY_MCP_CONFIG_PATH
Also confirm that the server definition still uses:
- name
decision-ops-mcp - URL
https://api.aidecisionops.com/mcp
The Tool Prompts For Login Every Time
Repeated login prompts usually mean the consent flow was started but not completed, or the tool call was not retried after consent. Finish the browser flow, then rerun the same MCP request. If the loop continues, check /integrations/agents to see whether the grant was created at all.
Consent Succeeds But Calls Still Fail
If the browser shows a successful authorization but the IDE still gets errors, look for one of these issues:
- the local MCP config still points to an old server definition
- the grant was created for a different organization than the one you expected
- the IDE cached stale settings and needs a reload or restart
The connected clients list on /integrations/agents is the fastest place to verify whether the authorization actually belongs to the current workspace.
Search Or Publish Uses The Wrong Context
If search results feel unrelated or publish lands in the wrong scope, the integration is usually healthy but configured with the wrong organization, project, or repository values. Regenerate the install details from /integrations/agents, update the config, and retry. This matters most for user-level integrations like Codex and Antigravity, where one stale config can affect multiple repositories.
The Client Is Connected But Access Is Denied
A visible grant does not guarantee that every action is allowed. If the IDE can connect but publish or validation is denied, check whether your role in that organization actually permits the requested operation. The MCP grant represents you; it does not bypass workspace permissions.
Where To Go Next
If the issue is clearly tied to one platform, go back to the relevant setup guide:
connect-from-codex.mdconnect-from-claude-code.mdconnect-from-cursor.mdconnect-from-vscode.mdconnect-from-antigravity.md
If the problem looks more like a product error than an IDE-specific one, continue with ../reference/common-errors.md.