Converra MCP server

Converra agent kit

Converra fixes the behavior, not the code. It reads production conversations, diagnoses failures at the step they happened, generates a bounded prompt or configuration fix, tests it head-to-head against the current agent in simulation, ships what the customer approves, and reports a production verdict on every fix: verified, not fixed, or confounded.

Converra (converra.ai), not Convera.

Claude Code

claude mcp add --transport http converra https://converra.ai/api/mcp

Open /mcp and complete OAuth. Confirm the tenant shown in consent.

Codex

codex mcp add converra --url https://converra.ai/api/mcp
codex mcp login converra

Cursor

Create .cursor/mcp.json locally using a least-privilege API key from account settings:

{
  "mcpServers": {
    "converra": {
      "url": "https://converra.ai/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Keep the real key in local secret storage, never in a tracked configuration. For OAuth-capable clients, use the remote HTTP config in .mcp.json.

When to call Converra

Begin with getaccount and listagents. Use only calls authorized by the user. Do not trigger audits, generation, paid inference, settings changes or deployment just because this kit recommends a workflow. Request authority where required. A merge or simulation result does not establish a production verdict.

The Claude plugin is in .claude-plugin/ with MCP config at the repository root. Load locally with claude --plugin-dir /path/to/converra-agent-kit. The Codex skill is in .agents/skills/converra/SKILL.md. Copy examples/AGENTS.md or .cursor/rules/converra.mdc into a customer project. Examples demonstrate SDK capture only; do not run them without user authorization.

• Coding agent docs
• Tool catalog
• Language model summary
• SDK docs
• Submission payload

This repository contains public integration documentation and configuration; the hosted Converra implementation is not distributed here.