dbtrail CloudAPI Reference
MCP
Model Context Protocol endpoint for AI tool integration
The MCP endpoint provides AI clients with access to dbtrail Cloud tools via the Model Context Protocol (Streamable HTTP). Requires the mcp:connect permission.
Endpoint
| Method | Endpoint | Permission | Description |
|---|---|---|---|
POST | /mcp | mcp:connect | MCP Streamable HTTP endpoint |
DELETE | /mcp | mcp:connect | Terminate an MCP session |
GET /mcp returns 405 — SSE streaming is not supported.
Tools
The gateway serves the following tools:
| Tool | Description |
|---|---|
query | Query indexed binlog change events with before/after row images |
batch_query | Query up to 10 tables concurrently in a single call |
count_events | Aggregate event counts, optionally grouped by schema, table, or event type |
list_tables | List schemas and tables with indexed binlog data on a server |
list_schema_changes | List DDL events (CREATE, ALTER, DROP, RENAME, TRUNCATE) |
list_servers | List registered MySQL servers for the current tenant |
status | Streaming health, replication position, and index coverage |
recover | Generate point-in-time recovery SQL — always dry-run, never executed |
forensics_capabilities | Check available forensic data sources on a server |
who_changed | Trace who modified a specific row (user, host, client program) |
user_activity | Recent SQL statements by a specific MySQL user |
connection_history | Connections from a specific MySQL user or host |
search_docs | Search dbtrail product documentation |
read_doc | Read the full content of a documentation page |
The forensic tools (forensics_capabilities, who_changed, user_activity, connection_history) require a plan with the forensics feature (Pro or higher).
See Claude Integration for setup instructions and Tools Reference for per-tool parameters and responses.