Connect Gummble MCP to Bolt
Add Gummble as a custom HTTP MCP connector in Bolt for evidence-led UI generation.
Connect Gummble to Bolt to bring source-linked product design evidence into your prompt before Bolt generates UI.
This guide uses Bolt's documented custom MCP connector. It does not imply a built-in Bolt connector, official listing, partnership, or endorsement.
1. Open Connectors
Open Bolt's Connectors (MCP) page and choose Custom MCP server. You can also reach Connectors from the prompt box.
2. Add Gummble
| Field | Value |
|---|---|
| Name | Gummble |
| URL | https://mcp.gummble.com/mcp |
| Transport type | HTTP |
| Authentication | MCP OAuth |
Click Connect, sign in to Gummble in the browser, approve access, and return to Bolt.
3. Review the tools
Bolt turns a connector's available tools on by default. Review the list and confirm it matches Gummble's current read-only MCP tools. Tool settings apply across projects, so leave enabled only the tools you intend Bolt to use.
4. Research before building
Use Gummble to compare shipped mobile subscription paywalls that explain
annual value clearly. Return three source links and a short hierarchy
checklist, then build the paywall without copying any one product.For onboarding:
Use Gummble to find browsable onboarding flow sequences for collaborative apps.
Compare steps, progress framing, permission timing, and first value. Cite
the source links before implementing our flow.Troubleshooting
- If Gummble is connected but Bolt does not use it, mention Gummble by name and verify its tools are enabled in connector settings.
- If the tool inventory changes, refresh or reconnect the connector and review the list again.
- For OAuth, plan, scope, or empty-tool failures, see MCP troubleshooting.
Review Gummble MCP access and connect your account.
Official Bolt reference: Connect to an MCP server.