Guide

MCP integration

Connect your coding agent to Catch — it can create apps, create access keys, fetch setup instructions, and read feedback without leaving the editor.

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 server is at https://catch.dev/mcp (streamable HTTP).

Claude Code

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

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

{
  "mcpServers": {
    "catch": {
      "url": "https://catch.dev/mcp"
    }
  }
}

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:

Permission	Allows
Set up integrations	Create apps and access keys, and read setup instructions
View apps & feedback	List apps and read feedback reports

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

Tool	Needs	Does
`whoami`	—	The signed-in user, their organizations, and the granted permissions
`find_organizations`	either permission	Lists organizations you belong to
`find_projects`	either permission	Lists the apps in an organization
`create_project`	Set up integrations	Creates an app and provisions its first access key in one call
`create_access_key`	Set up integrations	Creates an additional access key for an existing app
`get_setup_instructions`	either permission	Install and init instructions for an app on `web`, `ios`, or `android`
`find_feedback`	View apps & feedback	Recent feedback reports for an organization, optionally one app (up to 50)

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:

whoami — confirm the user, organization slugs, and granted permissions.
find_projects for the target organization; create_project if the app doesn't exist yet (it returns an access key).
get_setup_instructions with the app's organizationSlug, projectSlug, and platform (web, ios, or android).
Apply the returned snippet in the host codebase, keeping the access key exactly as given.
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.

Android

Collect user feedback from your Android app with shake-to-report — screenshot, annotation, and a note, straight to your dashboard.