Skip to main content

Start with the MCP Server

The Kotzilla MCP Server is the fastest path from zero to fixing production issues in your app. Once installed in your AI coding assistant, a single prompt registers your app on the Kotzilla Platform and applies all SDK changes to your project, so your first captured session is ready for root cause analysis and guided fixes.

Prerequisites​

  • An MCP-compatible tool (Claude Code, Cursor, Windsurf, Android Studio, or any other MCP-compatible assistant).
  • A Kotzilla account. If you do not have one yet, create a free account at console.kotzilla.io.
  • Access to the project files for the app you want to monitor.

Step 1: Install the MCP Server​

Claude Code: run

claude mcp add --transport http kotzilla https://mcp.kotzilla.io/mcp

Codex: run

codex mcp add kotzilla --url https://mcp.kotzilla.io/mcp

Clients that add servers by URL (Cursor, Junie, AI Assistant): use https://mcp.kotzilla.io/mcp directly.

Or ask your assistant:

Set up Kotzilla MCP server using https://kotzilla.io/llms.txt

Other clients​

Add this to your AI assistant's MCP configuration (requires Node.js):

{
"mcpServers": {
"kotzilla": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.kotzilla.io/mcp"]
}
}
}

Step 2: Sign in to Kotzilla​

Sign in to Kotzilla in your browser to authorize the MCP Server. If you do not have an account yet, switch to the Sign up tab to create a free one. Then approve access for Kotzilla MCP.

Most tools open the sign-in window automatically on first use. If the window does not open, or if you closed it before finishing, start the sign-in from your tool:

  • Claude Code: run /mcp, select kotzilla, then choose Authenticate.
  • Codex: run codex mcp login kotzilla.
  • Clients connected by URL (Cursor, Junie, AI Assistant): open the MCP settings of your client, select kotzilla, then choose Authenticate.
  • mcp-remote: restart your assistant, then complete the sign-in within about 2 minutes, in the most recent browser tab. Older tabs return an "Unauthorized" error.

If your client shows "Sign in required" without a way to sign in, use the mcp-remote configuration from Step 1.

Step 3: Register your app and set up the SDK​

In your assistant, ask:

Register my app on Kotzilla and set up the SDK

The assistant will:

  1. Read your project structure to detect the package name and app type.
  2. Register the app on the Kotzilla Platform.
  3. Apply all SDK changes: version catalog entries, Gradle plugin, kotzilla.json, and the SDK initialization. The assistant detects whether your app uses Koin and wires it accordingly; it does not add a Koin container if you do not use one.

Review the proposed changes, sync the project, and run a build.

Step 4: Capture your first session and start asking​

Run your app. As soon as the first session is captured, you can start asking performance and stability questions through natural language. See What you can ask for example prompts covering reports, version comparison, root cause analysis, crash investigation, and guided fixes.

Manual setup​

If you prefer to set up the SDK manually without MCP tools, use one of the following flows:

You can then follow the dedicated SDK setup steps for your app type:

Technical requirements​

The MCP Server works with any project that meets the Kotzilla SDK requirements. See the Get started overview for the full supported matrix.

info

Questions or issues during setup? Contact us. We are here to help!