Gummble MCP for Bolt
Add Gummble to Bolt through Bolt's custom MCP connector route.
Use Gummble in Bolt to bring source-linked product evidence into the project before Bolt generates UI.
Verification status: this is Bolt's documented custom MCP route. Gummble is not claiming a built-in connector, official integration, partnership, listing, or completed Bolt-specific production receipt. Authenticated clean-account verification is pending.
1. Open connector settings
From the Bolt homepage chatbox:
- Click the + icon.
- Select Connectors.
- Select Manage connectors.
- Choose Custom MCP server.
2. Add Gummble
| Field | Value |
|---|---|
| Name | Gummble |
| URL | https://mcp.gummble.com/mcp |
| Transport type | HTTP |
| Authentication | MCP OAuth |
Click Connect, complete Gummble sign-in and consent, then return to Bolt.
3. Review tools and project access
Bolt enables a connector's available tools by default. Review the tool list and confirm it matches Gummble's 14 read-only tools. Tool selection applies across projects, while the connector itself can be turned on or off for each project.
Enable Gummble only for projects where design-reference context is useful.
4. Research before building
Use Gummble to compare shipped mobile subscription paywalls that explain
annual value clearly. Return source links and a short hierarchy checklist,
then build the paywall.A release receipt must cover OAuth, the 14-tool inventory, one useful search, one recoverable failure, the per-project toggle, refresh, revoke, and reconnect behavior.
Troubleshooting
- If Gummble is connected but unavailable in chat, turn it on from the project's Connectors menu.
- If tools have changed, use Refresh connection and review the list again.
- For OAuth or scope failures, see MCP Troubleshooting.
Before connecting, review current Gummble MCP access and plan options. Gummble verifies account entitlement during OAuth; Bolt never receives a static Gummble credential.
Official platform reference: Connect to an MCP server.