TrapFall includes a Model Context Protocol (MCP) server for AI agent integration. Communicates via stdio JSON-RPC 2.0.
trapfall mcpUses the same database as set by --db flag or TRAPFALL_DATABASE_URL env var.
Configure your AI client to run this command as an MCP server.
| Tool | Description |
|---|---|
list_issues |
List issues for a project (with filters) |
get_issue |
Get issue detail by ID |
get_event |
Get event detail by ID |
set_status |
Set issue status (resolved/unresolved/ignored) |
search_issues |
Search issues by query string |
list_projects |
List all projects |
get_project |
Get project detail by slug |
get_project_stats |
Get issue/event counts for a project |
list_alert_rules |
List alert rules for a project |
list_events |
List events for an issue |
rotate_dsn |
Generate new DSN key for a project |
healthcheck |
Check server health |
An AI agent connected via MCP can:
- Monitor errors —
list_issuesto check for new errors - Investigate —
get_issue+list_eventsto see full stack traces - Take action —
set_statusto resolve or ignore issues - Search —
search_issuesto find specific errors - Manage projects —
list_projects,get_project_stats
stdio only. No TCP. This is by design — MCP servers are launched as child processes by the AI client.