Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Strada MCP

Strada exposes the same CLI tools over MCP. Cursor, Claude, and VS Code can list issues, read logs, and run SQL.
Prefer the remote HTTP server when the agent should log in with OAuth. Keep local strada mcp when you already use the CLI in that folder.
Cursor / Claude / VS Code │ │ POST https://strada.sh/mcp (OAuth JWT) ▼ ┌─────────────┐ │ /mcp │ same tools as `strada issues list` └──────┬──────┘ │ ▼ issues_list logs query traces_view analytics_pages │ ▼ Strada website API ► your ClickHouse / Tinybird

Remote HTTP MCP

Add this URL in the MCP client:
https://strada.sh/mcp
The client starts OAuth. Sign in with Google, then Allow access on /consent. After that, tools such as issues_list and query work.
Remote MCP has no folder defaults. Pass --project and --org on tools that need them.
Preview uses https://preview.strada.sh/mcp.

Local stdio MCP

The strada binary is also a stdio MCP server. Run strada mcp after strada login. The client starts the process and talks JSON-RPC on stdin and stdout. Do not pipe other output into that process.
Folder strada setup still selects the default org and project for stdio.

What agents can do

Once the server is installed, an agent can:
  • List and inspect issues with issues_list and issues_view
  • Read logs around a failure with logs
  • Open a trace with traces_view
  • Run SQL with query
  • Check traffic with analytics_pages and analytics_events
Those tools are the CLI commands, with spaces turned into underscores. strada issues list is the issues_list tool.

What is not a tool

These stay in the terminal:
  • login. Device flow. Opens a browser and needs a TTY.
  • logout. Clears the shared local session that other MCP tools need.
  • database create. Tinybird OAuth and workspace bootstrap.
  • database upgrade. Long-running Clack output that would break stdio.
  • mcp. The stdio server command itself.
  • The TUI. strada with no arguments.
setup and the rest of the query and mutate commands are tools. setup needs --org and --project when stdin is not a TTY. MCP includes mutation tools such as issues_resolve and projects_delete.

Next

  1. Install the server in Cursor, Claude Desktop, or VS Code
  2. Use the Tools group in this tab for the generated schema of each command