Give your AI agent your production errors, read-only
Condux exposes a Model Context Protocol endpoint, so Claude, Cursor or any MCP client can list issues, read a de-minified stack trace and page through real occurrences. It is read-only, it burns no fix allowance, and its token resolves to exactly one project.
Debugging with an agent usually means pasting a stack trace into a chat window. An MCP endpoint removes that step: the agent queries the errors themselves, in your editor, against what actually broke in production. The interesting question is what you had to hand over to get that, and the answer here is one project, read-only.
Connect a client
Mint a token in the project's MCP tab, then paste the config your client generated it for.
{"mcpServers": {"condux": {"url": "https://app.condux.ai/api/mcp","headers": { "Authorization": "Bearer condux_mcp_..." }}}}
What the agent can do
- list_issues
Search and filter issues with the same query grammar as the dashboard, by status, level or assignee.
- get_issue
Read one issue with its latest event, including stack frames resolved through your uploaded source maps.
- list_issue_events
Page through real occurrences of an issue, so the agent sees the pattern rather than one sample.
What it deliberately cannot do
The scope is the feature. An agent credential is only as safe as the smallest thing it can reach.
- No write path
There are no write tools. The endpoint cannot change an issue, a project or a setting, because nothing on it does.
- One project per token
A token resolves to a single project. It is not an account credential and it cannot reach a second project.
- No allowance to burn
Reading errors through MCP costs no Conductor fix runs, so an exploring agent cannot spend your month.
- Already scrubbed
Events are scrubbed of PII at ingest, so the agent sees exactly what the dashboard shows and nothing more.
Frequently asked questions
Can the agent change anything in Condux?
No. The endpoint exposes three read tools and no write tools at all, so there is nothing for an agent to change even if it tried. Triage still happens in the dashboard, by a person.
Does using MCP consume my AI fix allowance?
No. The allowance covers Conductor runs, which open draft pull requests. Reading issues over MCP is free and unmetered.
Which clients work?
Any MCP client that can talk to a remote HTTP server and send a custom header, which includes Claude and Cursor. Condux speaks JSON-RPC 2.0 over Streamable HTTP.
Does it work when I self-host?
Yes. The endpoint is part of the control plane, so a self-hosted Condux serves it from your own deployment with no extra service to run.