Kensa's MCP server lets your coding agent read issues and report deployed fixes.
Connect
From your application repository, use the setup prompt. It adds
https://kensa.sh/api/mcp to your coding agent's project configuration. You can also copy the
configuration from Settings → MCP server. Each developer signs in separately; credentials stay
outside the repository.
| Coding agent | Sign in |
|---|---|
| Claude Code | Open /mcp and sign in. |
| Codex | Run codex mcp login kensa. |
| Cursor | Click Connect in its MCP settings. |
| OpenCode | Run opencode mcp auth kensa. |
A browser opens for you to choose a project and approve access. Check that the connected project is the one you intended. If Kensa's tools don't appear, restart your agent session.
To send traces, set up a project API key or Langfuse connection separately. See Tracing.
Use Kensa
Ask your coding agent:
Show me the issues in this project.For a specific issue, use its ID:
Investigate and fix Kensa issue <issue ID> in this repo. Once the fix is deployed, report the deployed version to Kensa.See the Agent workflow for investigating issues and the Tool reference for available tools.