Condux error monitoring

ai.conduxPublished by condux.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote, read-only MCP endpoint for Condux error monitoring that lets an assistant inspect a project's issues, events and deminified stack traces.

What you can do
List and read issues in a Condux project, including stack traces deminified with source maps and tag facets and breadcrumbs shown in the dashboard description (no tool list is published, so exact tool names are unknown). Page through occurrences of an issue to see individual events. Use the data to help triage and debug production errors; the endpoint itself offers no write tools.
When to use it
Useful when an assistant should debug against real production errors from a Condux-monitored application, for example reading grouped issues and stack traces while investigating a bug. It fits teams already sending errors to Condux who want an AI client to look at them without leaving the chat.
Requirements
A remote MCP endpoint at app.condux.ai over streamable HTTP. Requires a Condux account and a project-scoped MCP token from the project's MCP tab, sent as a Bearer token in the Authorization header. Each token resolves to exactly one project.
Before you install
The Authorization header carries a secret MCP token; keep it out of logs and shared configs. The token is scoped to a single project, so it exposes that project's production error data, including stack traces and breadcrumbs, to the connected AI client. The endpoint is described as read-only with no write tools.

Installation

In SourceWeft

  1. Open Condux error monitoring in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.condux%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "condux-error-monitoring": {
      "type": "http",
      "url": "https://app.condux.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Condux

Condux is a source-available error monitoring platform with a built-in AI fix engine.

[An issue in Condux, with its stack trace, source context, volume chart and triage actions]

SDKs report errors to a stateless ingest relay, which authenticates the DSN, applies per-plan rate limits and quotas, and scrubs PII before buffering through Redpanda. A consumer fingerprints and groups events into issues, writes time series to ClickHouse and issue state to PostgreSQL. A Next.js dashboard reads that back as grouped issues with stack traces, breadcrumbs, tag facets and per-hour charts, and alerting fires on new and regressed issues to email, Slack, Discord and webhooks.

The Conductor

The fix engine takes an issue to a draft pull request. It assembles a scoped, scrubbed context from the stack trace and the project's code mappings, sends it to Claude or to a model the organisation supplies, and applies the returned changes on a new branch as a draft pull request. Fixes are never merged automatically.

[A Conductor fix run on an issue, showing its status, the model token usage and the draft pull request it opened]

Repository access is a GitHub App with short-lived installation tokens; the model is not given the token. After a fix PR merges, a verification loop compares the issue against its subsequent event counts and resolves it once it stays silent for a configured window.

Open Dependabot findings on a connected repository can be turned into dependency-bump draft PRs through the same engine.

Each run is metered against the organisation's monthly allowance and a spend ceiling, with per-run cost derived from recorded model token usage.

Compatibility

Ingestion accepts the Sentry envelope and store formats, so an existing Sentry SDK reports to Condux by changing its DSN. OTLP/HTTP logs are also accepted, which lets an OpenTelemetry-instrumented application report without an SDK.

First-party SDKs are published for JavaScript/Node, browser, edge, Next.js, Python, Go, Ruby, PHP, JVM and .NET, with framework adapters for React, Express, Flask/Django/FastAPI, Rails, ASP.NET Core and Spring Boot. The SDKs are Apache-2.0; the server is FSL.

MCP endpoint

A read-only Model Context Protocol endpoint lets an AI agent debug against real production errors. Point Claude, Cursor or any MCP client at a project with a scoped token and it can list issues, read stack traces and page through occurrences. There are no write tools, and a token resolves to exactly one project.

[The MCP tab of a project, where a scoped read-only token is minted with its client configuration snippet]

Architecture

.NET 10 services and a Next.js / React / TypeScript dashboard.

 SDKs ──envelope──▶ [Relay] ──▶ [Redpanda] ──▶ [Consumer] ──▶ ClickHouse (events, time series)                                                          └──▶ PostgreSQL (issues, orgs, audit) Dashboard ──▶ [ControlPlane] ──▶ [Conductor] ──▶ draft PR

Valkey backs rate limiting and monthly quotas. The relay holds no state. Raw events expire per plan through a column-driven ClickHouse TTL rather than a scheduled job.

Repository layout

PathContents
backend/.NET solution: Condux.Relay (ingest), Condux.ControlPlane (API), Condux.Consumer, Condux.Conductor (fix engine), Condux.Core (scrubbing, grouping, plans, quotas)
web/Next.js dashboard
sdks/Client SDKs and framework adapters
packages/Shared frontend packages
proto/Protobuf contracts
migrations/PostgreSQL and ClickHouse schema, numbered and idempotent
contracts/Exported OpenAPI document and Postman collection
deploy/Docker Compose stack and Helm chart
examples/Sample applications that report errors

Requirements

  • .NET SDK 10.0 or later
  • Node 22 or later, with pnpm
  • Docker and Compose

Running it

bash
cp deploy/.env.example deploy/.envdocker compose --env-file deploy/.env -f deploy/docker-compose.yml up -d

The dashboard is at http://localhost:3200 and the API on 8080.

Building and testing from source:

bash
cd backend && dotnet build Condux.sln -c Releasecd backend && dotnet test Condux.sln --filter "Category!=Integration"cd web && pnpm install && pnpm build

Integration tests start real datastores through Testcontainers and bind the same ports as the Compose stack, so run them with that stack stopped.

Deployment

deploy/docker-compose.yml runs the whole platform on a single host. deploy/charts/condux is a Helm chart that deploys the services against externally managed PostgreSQL, ClickHouse and a Kafka-API broker rather than running datastores in the cluster. Its README.md covers the values, including config.ingestHost, which is required because every DSN the control plane mints points at it. You build and push the service images yourself; the chart does not ship any.

Security

Report suspected vulnerabilities privately by email as described in SECURITY.md, rather than in a public issue or pull request.

License

Condux is source-available under the Functional Source License (FSL-1.1-ALv2). It may be read, self-hosted and modified for any purpose other than offering a competing commercial service, and each release converts to Apache-2.0 two years after it is published.

See LICENSE for the terms and LICENSING.md for a plain-language summary. The SDKs under sdks/ are Apache-2.0.

Source: README.md at commit 746fc37

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 13, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.