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.

What You Need First

Before you start, confirm that you have:

• Claude Code installed
• the repository checked out locally
• access to the DecisionOps organization and project that should govern this repository
• permission to edit {repo_path}/.mcp.json

The current platform catalog lists these default server values:

• server name: decision-ops-mcp
• server URL: https://api.aidecisionops.com/mcp

Add The MCP Server

In the DecisionOps dashboard, open /integrations/agents and choose Claude Code. Select the organization, project, and repository context that matches the repository in front of you. Then copy the generated install details.

Open {repo_path}/.mcp.json in the repository and add or verify the DecisionOps server entry. Because this file is project-scoped, it is usually better to keep it aligned with the repository’s actual policy context instead of copying a personal global setup from another tool.

If the repository already has an MCP config, update the existing DecisionOps entry rather than adding a second one with a slightly different name. The server name should remain decision-ops-mcp so Claude Code can discover the correct target consistently.

Complete The First-Run Consent

Invoke any DecisionOps MCP tool from Claude Code. On the first run, the server returns an auth challenge and Claude Code opens the DecisionOps browser flow. Sign in if needed, confirm the organization, and approve the requested access.

After the browser flow finishes, go back to Claude Code and retry the same tool call. That retry is important. Completing consent does not automatically rerun the original request.

Confirm The Setup

Return to /integrations/agents and verify that Claude Code appears in the connected client list. Once it does, you can use the common IDE guides to search for earlier decisions, draft a new record, validate it, and publish it directly from Claude Code.

Troubleshooting

If Claude Code does not see the server, double-check that .mcp.json was added to the correct repository. If consent succeeded in the browser but tools still fail, retry the same tool call before changing the config. If you expected a machine-wide setup, keep in mind that Claude Code is currently documented as a project-scoped integration, so each repository should have the MCP file it needs.