Connect Gummble MCP to Kiro

Configure Gummble as a remote MCP server in Kiro for source-linked product design research.

Connect Gummble to Kiro to research real product screens, browsable flow sequences, UI patterns, and microcopy before implementing UI.

This guide uses Kiro's documented custom remote MCP configuration. It does not imply a Kiro server-directory listing, Power, partnership, or endorsement.

1. Open an MCP configuration

From the Command Palette, choose one of:

Kiro: Open workspace MCP config (JSON) for .kiro/settings/mcp.json.
Kiro: Open user MCP config (JSON) for ~/.kiro/settings/mcp.json.

Workspace configuration applies to one project. User configuration applies across workspaces.

2. Add Gummble

{
  "mcpServers": {
    "gummble": {
      "url": "https://mcp.gummble.com/mcp",
      "disabled": false,
      "autoApprove": [],
      "disabledTools": []
    }
  }
}

Save the file. Kiro applies MCP configuration changes automatically. Keep autoApprove empty while you review the tool behavior.

Kiro handles browser OAuth for compatible remote servers. Gummble supports Dynamic Client Registration, so no static client ID, client secret, API key, or authorization header belongs in this configuration.

Follow the browser prompt, sign in to Gummble, approve access, and return to Kiro.

4. Verify with a bounded task

Use Gummble to research three real onboarding flows for an AI note-taking
app. Compare the sequence, first-value moment, and source links before
proposing our implementation.

Review Gummble's current read-only MCP tools before approving calls. Expand to comparison or batch tools only after the first search returns relevant source links.

Directory and Power status

Kiro documents one-click MCP links and public Powers. This page describes the custom configuration route only. Do not describe Gummble as listed in Kiro's server directory or published as a Power unless it appears in the corresponding live catalog.

Troubleshooting

If the server is disabled, set disabled to false.
If a token expires, use Kiro's Re-authenticate action.
If a team policy blocks custom servers, ask the workspace administrator to review the configuration.
For general auth and scope failures, see MCP troubleshooting.

Review Gummble MCP access and connect your account.

Official Kiro references: MCP configuration, MCP servers, and Power submission.