Connect Gummble MCP to Lovable
Add Gummble as a custom Lovable MCP personal connector for UI research while you build.
Connect Gummble to Lovable when you want the Lovable Agent to research real screens, flows, UI patterns, and microcopy before it generates an onboarding flow, paywall, empty state, checkout, or marketing page.
Lovable supports custom MCP servers as personal connectors on all plans. This setup provides build-time context to the Lovable Agent; it does not add Gummble to the app you publish.
1. Open the connector catalog
In Lovable, open Connectors, select All, then choose Custom MCP. Lovable manages custom MCP servers as personal connectors, so each teammate authorizes their own connection.
2. Add Gummble MCP
Enter:
| Field | Value |
|---|---|
| Server name | Gummble |
| Server URL | https://mcp.gummble.com/mcp |
| Authentication | OAuth |
Click Add & authorize, sign in to Gummble, approve MCP access, and return to Lovable. Do not put an API key or bearer token in the connector form; Gummble uses browser OAuth.
3. Research before Lovable builds
Mention Gummble explicitly in your prompt:
Use Gummble to find real SaaS empty states for a new project with no
imported data. Compare first-use guidance, recovery actions, and permission
states. Cite the Gummble source links, then build the page.For a higher-intent conversion flow:
Use Gummble to compare mobile subscription paywalls with annual savings,
trial disclosure, and restore-purchase actions. Summarize the strongest
information hierarchy with source links, then implement a responsive
paywall without copying any one product.The connected server should expose Gummble's current read-only MCP tools. Start with one bounded search and inspect the returned source links before asking Lovable to generate UI.
What the connector can and cannot do
- Personal connectors belong to the person who connected them; teammates connect with their own credentials.
- The connector gives Lovable context while building and is not bundled into the deployed app.
- Workspace admins can restrict personal MCP connectors.
- If the published app needs Gummble at runtime, use a supported app/API integration architecture instead of this personal connector.
Troubleshooting
- If Custom MCP is unavailable, ask a workspace admin whether personal connectors or MCP access are restricted.
- If authorization or tool discovery fails, see MCP troubleshooting.
- If you need to revoke access, remove Gummble from Personal connectors and reconnect through OAuth.
Review Gummble MCP access and connect your account.
Official Lovable references: custom MCP integrations and integration types.