MCP

MCP Overview

The Model Context Protocol server for Gummble — stream design context into any agent.

The Gummble MCP server lets your AI tools call Gummble like a teammate. It implements the Streamable HTTP transport with OAuth 2.1 Resource Server semantics, so any standards-compliant MCP client (Claude Desktop, Cursor, Windsurf, Codex, v0, and other agent tools) can pull real product UI references into its workflow.

https://mcp.gummble.com/mcp

Quick setup

How auth works

  1. Your client POSTs to https://mcp.gummble.com/mcp without a token.
  2. The Worker replies 401 + WWW-Authenticate: Bearer realm="mcp", resource_metadata="https://mcp.gummble.com/.well-known/oauth-protected-resource/mcp".
  3. The client fetches the resource metadata → finds https://api.gummble.com as the authorization server.
  4. The client runs Dynamic Client Registration → opens an authorize URL in your browser → you sign in on gummble.com → consent → callback.
  5. The client exchanges the code for an access token (audience-bound to https://mcp.gummble.com/mcp) and retries the original MCP request.

That's it. There is no Gummble-specific code in any MCP client — they all do this dance the same way per the MCP + RFC 8414 + RFC 7591 specs.

If you're building an app that stores tokens and calls Gummble MCP on behalf of your users, use the Build an integration guide.

If install or auth fails, start with Troubleshooting.

Available tools

Browse the full list at Tools. High-level groups:

  • gummble.apps.* — list, get, search apps
  • gummble.screens.* — fetch and filter screens
  • gummble.flows.* — multi-step UX journeys
  • gummble.search.* — keyword + semantic + visual

Rate limits

Per-user, tracked on the Worker via Cloudflare KV. See Rate limits.