Agents & CLI
Machine credentials, the MCP server and the errordx CLI.
ErrorDX is agent-first: the same REST API surface is exposed as MCP tools and as a JSON CLI, authenticated with scoped agent keys.
Agent keys
Create keys in Settings → Members → Agent keys (or via
POST /api/v1/organizations/{slug}/agent-keys). The plaintext key (ak_…) is shown
once; only its SHA-256 hash is stored.
| Permission | Access |
|---|---|
read | list/get projects, issues, events, alerts |
write | create/update projects, triage issues, create alert rules, test ingest |
deploy | release/source-map uploads |
Keys are scoped to one organization, recorded in the agent audit trail
(GET /organizations/{slug}/agent-audit), and revocable at any time.
MCP server
Point any MCP client at https://api.errordx.com/mcp (streamable HTTP) with the
agent key as a Bearer token:
{
"mcpServers": {
"errordx": {
"url": "https://api.errordx.com/mcp",
"headers": { "Authorization": "Bearer ak_..." }
}
}
}Tools: project list/create, DSN lookup, issue search/detail/triage/comment/activity,
event listing/lookup, test ingest, alert rules and channels, release files,
API-token create/list/revoke (mint edx_… credentials for sentry-cli and CI).
CLI
cargo install --path crates/errordx-cli # builds the `errordx` binary
errordx auth set --url https://api.errordx.com --key ak_... --org acme
errordx projects list
errordx issues list --project web --status unresolved --query "TypeError"
errordx issues resolve <issue-id>
errordx ingest --project web --message "test event" # through the real DSN
errordx dsn web # copy-paste DSN for SDKsEvery command prints JSON; failures print {code, message} to stderr and exit 1.
Credentials resolve from flags, then ERRORDX_URL / ERRORDX_API_KEY / ERRORDX_ORG,
then ~/.config/errordx/config.json.