MCP integration

Catch runs an MCP (Model Context Protocol) server, so a coding agent — Claude Code, Cursor, or any MCP client — can work with your Catch account directly. A connected agent can create apps, create access keys, fetch platform-specific setup instructions, and read feedback reports: enough to integrate a Catch SDK into a codebase end to end.

Authentication is OAuth: the agent's first request opens a browser consent page on catch.dev. There are no API tokens to copy or store.

1. Connect

The address is scoped to one app: https://catch.dev/mcp/<organization>/<app>. Copy the exact address for an app from App → API Keys → Connect an AI agent — it is built for you there, so the slugs are always right.

Scoping matters. On an unscoped address the agent sees every app you can reach and picks one; with several apps it can wire your iOS project to the app you use for the web frontend, and nothing errors, because both are valid choices. A scoped address names the target, the server checks it when the agent connects, and the app-picking tools are not offered at all.

Claude Code

claude mcp add --transport http catch https://catch.dev/mcp/acme/web-app

Cursor / VS Code / other MCP clients — add to the client's MCP config:

{
  "mcpServers": {
    "catch": {
      "url": "https://catch.dev/mcp/acme/web-app"
    }
  }
}

Wider scopes: /mcp/<organization> covers every app in one organization, and a bare /mcp covers everything you can reach — useful for reading feedback across apps, not for setting one up. A bad slug is rejected when the agent connects, not later.

Staging: the same paths on https://staging.catch.dev. The setup instructions you get back carry the matching ingest endpoint, so an app wired from staging reports to staging.

2. Approve access

On the agent's first request, your browser opens a consent page. Sign in to catch.dev if you aren't already, then choose what the agent may do:

Grant only what the task needs. Setup instructions include a real access key only when Set up integrations is granted; otherwise they carry the ck_your_key placeholder and tell the agent to create a key first.

3. Integrate an app

Ask the agent to set up Catch — for example: "Add Catch feedback to this app and send a test report." The agent creates or finds the app, fetches the setup instructions for your platform — the same steps as the Web, iOS, and Android pages, condensed for direct application — applies the snippet, and verifies. The result to look for is a test report under App → Feedback in the dashboard.

Early access: the setup instructions install SDKs that aren't on the public registries yet — contact us for early access.

Tools

Heads up: create_project, create_access_key, and get_setup_instructions return real access keys, which end up in the agent's transcript — treat that transcript as sensitive.

For agents

The recommended flow to integrate an app:

1. whoami — confirm the user, organization slugs, and granted permissions.
2. find_projects for the target organization; create_project if the app doesn't exist yet (it returns an access key).
3. get_setup_instructions with the app's organizationSlug, projectSlug, and platform (web, ios, or android).
4. Apply the returned snippet in the host codebase, keeping the access key exactly as given.
5. Run the app and submit a test report, then confirm it arrived with find_feedback.

Disconnect

Open your profile and remove the client under Connected agents. Reconnecting runs the consent page again.