Connect Gummble MCP to Kilo Code

Connect Gummble to Kilo Code when an agent should research shipped product interfaces before it proposes UI or copy. Gummble exposes 14 read-only tools covering 300,000+ real UI screens, 21,000+ browsable flow sequences, UI patterns, product microcopy, and public App Store marketing screenshots across 1,500+ apps and sites.

Requirements

• A Gummble account on a plan that includes MCP access
• A current Kilo Code extension or Kilo CLI
• Browser access for the OAuth consent step

Use the exact MCP resource URL below. Do not append a query string or manually configure an Authorization header; Kilo adds the OAuth bearer header after authorization:

https://mcp.gummble.com/mcp

Option A: Kilo CLI

Add the remote server, then start OAuth:

kilo mcp add gummble --url https://mcp.gummble.com/mcp
kilo mcp auth gummble

Complete sign-in and consent in the browser. Back in the terminal, verify the server and OAuth state:

kilo mcp list
kilo mcp auth list

Use kilo mcp debug gummble only when the connection needs diagnosis. Redact OAuth metadata before sharing debug output.

Option B: project or global config

For a project, use ./kilo.json or ./.kilo/kilo.json. For all projects, use ~/.config/kilo/kilo.json:

{
  "mcp": {
    "gummble": {
      "type": "remote",
      "url": "https://mcp.gummble.com/mcp",
      "enabled": true,
      "timeout": 15000
    }
  }
}

Then run kilo mcp auth gummble and complete browser OAuth. Gummble supports Dynamic Client Registration, so no static client ID, client secret, API key, or bearer token belongs in the file.

Project configuration takes precedence over global configuration. Keep one intentional gummble entry to avoid testing a different URL than the one you edited.

Option C: Kilo Code settings

1. Open Kilo Code Settings.
2. Choose Agent Behaviour and then MCP Servers.
3. Add a remote HTTP server named gummble with https://mcp.gummble.com/mcp.
4. Start the authentication action when Kilo reports needs_auth.
5. Sign in to Gummble, approve consent, and return to the editor.

Choose Remote (HTTP), which uses Streamable HTTP for this connection. Gummble's legacy SSE URL is not needed for this setup.

Verify with one bounded request

Use gummble_search_screens once with q "mobile onboarding first step language
learning", platform "ios", limit 3, and include_images false. Return the app
name and Gummble source link for each result, then stop before changing files.

The result should contain real references and source links. Review the exact 14-tool inventory; every tool is marked read-only, non-destructive, and idempotent. The two App Store tools read Apple's public catalog, while the other 12 query Gummble's indexed library.

Troubleshooting

• Run kilo mcp list to confirm the server is enabled.
• Run kilo mcp auth list to inspect OAuth status.
• If authorization was revoked, run kilo mcp logout gummble, followed by kilo mcp auth gummble.
• If tools are unavailable, confirm the account plan includes MCP access.
• If a team policy blocks custom MCP servers, ask the workspace administrator to review the exact endpoint and read-only tool inventory.
• Use kilo mcp debug gummble for OAuth diagnostics, and redact the output.
• For shared recovery steps, see MCP troubleshooting.

Source and attribution boundary

Review Gummble MCP access and connect your account.

That link can attribute a guide visit and subsequent first-party session. The MCP resource URL itself must remain free of UTM parameters because OAuth binds tokens to the exact resource. Kilo client identity and OAuth client name can add directional activation evidence when the client reports a stable name, but custom names, proxies, cross-device sign-in, and copied configuration can make the source ambiguous. A guide click, OAuth event, or prepared Marketplace pull request does not by itself prove a qualified activation or paid conversion.

Official Kilo references: Using MCP in Kilo Code, Using MCP in the Kilo CLI, CLI command reference, and Marketplace contributions.