Skip to main content
Connect a coding agent to your workspace and it can query your telemetry with SQL, read the OnePatch agent’s incident investigations, and start or reply to workspace chats. Everything is scoped to your organization. The only writes are starting a chat and replying to one. Claude Code, Codex, and Cursor get a plugin. Everything else connects to the MCP server directly.

Install the plugin

The onepatch CLI wires every coding agent on your machine in one step.
Without Node, install the standalone binary instead:
onepatch install detects Claude Code, Codex, and Cursor and installs the OnePatch plugin in each. Pass an agent name to set up only one, as in onepatch install cursor. Each plugin can also be installed by hand.
Codex also needs the MCP server in ~/.codex/config.toml:
The first call opens an OAuth sign-in with your OnePatch account. In Claude Code, run /mcp to sign in. In Codex, run codex mcp login onepatch. In Cursor, sign in under Settings, MCP.

Other MCP clients

Any MCP client that speaks streamable HTTP can connect without a plugin.
Config files: .vscode/mcp.json (VS Code), ~/.codeium/windsurf/mcp_config.json (Windsurf). Reload the window after editing. The first call opens an OAuth sign-in with your OnePatch account. For a script, CI job, or unattended agent that can’t open a browser, use an API key. See MCP server.