Stitch MCP
Provides an authenticated OAuth proxy to Google Stitch's MCP API, allowing clients such as ChatGPT to connect using a Stitch API key and access Stitch project capabilities, including listing Stitch projects.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Google Stitch MCP on Cloudflare
MIT-licensed community bridge between ChatGPT and Google's Stitch MCP. Not affiliated with Google, OpenAI, or Cloudflare.
Connect from ChatGPT web
Open Plugins → + → Add custom MCP server.
Name it Stitch MCP. Use
https://stitch-mcp.tranvantu4444.workers.dev/mcpfor the maintained deployment, or your own deployed endpoint.Choose OAuth. Discovery provides the endpoints automatically. If advanced settings ask for a client setup method, select Dynamic client registration (DCR). No client secret is required. Scopes:
stitch offline_access.Review the connection warning and create the plugin. Complete authorization when prompted.
On the Stitch Cloudflare authorization page, enter your Stitch API key and explicitly approve access. Never enter your Gmail password or put the key in chat.
Install/select the resulting plugin in a conversation and ask List my Stitch projects.
Generate a key at Google Stitch → profile → Stitch settings → API key.
The old downloadable plugin package did not establish a ChatGPT web connection. Use Add custom MCP server above. The portable example now declares OAuth, but packaging alone still does not activate a web connection.
If ChatGPT cached the old OAuth-discovery failure, close and reopen the creation dialog and enter the same server URL again. Do not select no authentication.
Related MCP server: Generic Google Workspace MCP Server
Authentication and data handling
ChatGPT → OAuth access token → Cloudflare → Stitch API key → Google Stitch.
OAuth authorization code flow with S256 PKCE and dynamic registration of public clients.
Redirects restricted to the documented ChatGPT HTTPS callback paths and exactly matched to the registered client.
Explicit consent, same-origin form submissions, short-lived CSRF cookie, and one-time authorization transaction.
Read-only Google MCP initialization validates the key before storing a grant. No screen is generated as a connection test.
API keys encrypted with AES-256-GCM, bound to individual grants. Encryption key is a Cloudflare secret.
Opaque access/refresh tokens stored as SHA-256 hashes. Access expires after one hour; refresh rotates on each use. Authorization codes expire after five minutes and are consumed atomically.
Grants expire after 30 days, requiring reauthorization. Revocation disables every access/refresh token for the affected grant immediately.
Daily cleanup removes expired records. Hosting backups may retain deleted encrypted records under Cloudflare's retention policy.
The proxy operator can process credentials and traffic at runtime. Self-host if you do not trust the operator. Source is open; this is not an independent security certification. No OIDC email identity, Google sign-in, or enterprise verified-email integration is implemented.
Revoke access
Open /manage on your Worker and enter the same Stitch key to revoke its stored connections. Alternatively, OAuth clients can POST token and client_id to /revoke. Disconnecting in ChatGPT should not be assumed to call revocation. Revoking the API key in Google Stitch also blocks upstream use.
Self-host
Requirements: Node.js 22.13+ (tests use built-in SQLite), npm, Cloudflare Workers and D1 access.
git clone https://github.com/FourTran4444/googleStitchMCP.git
cd googleStitchMCP
npm test
npx wrangler@4 login
npx wrangler@4 d1 create stitch-mcp-oauthEdit wrangler.toml: choose your Worker name, set PUBLIC_ORIGIN to its exact HTTPS origin (no trailing slash), and replace the D1 ID with the one returned above. The checked-in IDs describe the maintained deployment, not credentials; forks must use their own resources.
npx wrangler@4 d1 migrations apply stitch-mcp-oauth --remote
npx wrangler@4 secret put ENCRYPTION_KEY
npx wrangler@4 deployAt the secret prompt, enter a cryptographically random 32-byte base64url value generated locally (for example with node -e "console.log(require('crypto').randomBytes(32).toString('base64url'))"). Keep it out of Git. Losing or replacing it invalidates existing encrypted credentials; revoke old grants before rotating it. Never use a Stitch key as the encryption key.
Cloudflare dashboard Git integration: connect this repository to the Worker, production branch main, root repository directory, build command npm test && npm run check, deploy command npx wrangler@4 deploy. Provision D1, apply migrations, and configure the encryption secret before the first deployment. Keep Node.js at 22.13+ or 24.
No paid-plan upgrade is required by this code. Provider quotas and usage charges depend on your account. Deployments are public endpoints; rate limiting is an operator responsibility.
Endpoints
Path | Purpose |
| Authenticated Streamable HTTP proxy |
| Resource discovery |
| OAuth discovery |
| Dynamic public-client registration |
| Credential entry and consent |
| Code exchange and refresh rotation |
| Token-based grant revocation |
| Key-based connection revocation |
| Proxy liveness only |
Clients supporting secure custom headers can still send X-Goog-Api-Key directly. ChatGPT web uses OAuth. The fixed upstream is https://stitch.googleapis.com/mcp; credentials are never forwarded on redirects, and mutations are not automatically retried.
Verification
npm test
npm run check
curl https://YOUR-WORKER.YOUR-SUBDOMAIN.workers.dev/.well-known/oauth-authorization-server
curl -i -X POST https://YOUR-WORKER.YOUR-SUBDOMAIN.workers.dev/mcpExpect discovery JSON with S256 PKCE and DCR, and an unauthenticated MCP 401 containing WWW-Authenticate. Unit tests use real SQLite and Web Crypto with mocked Google responses. Live Google access and actual ChatGPT design creation require a real user key and must be verified separately; deployment or a successful health check is not evidence of that acceptance.
See SECURITY.md, CONTRIBUTING.md, and MIT license.
References: OpenAI OAuth requirements, Google Stitch API-key configuration.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Manage Google Ads from ChatGPT, Claude or any MCP client. Sign in with OAuth or use an API key.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
The Stytch MCP server is a reference implementation that demonstrates remote MCP server authentication and authorization using Stytch Connected Apps. It provides OAuth 2.1-compliant authorization (including PKCE), Dynamic Client Registration, and validates Stytch-issued access tokens to enable AI agents to securely interact with external services through permissioned access, supporting scopes like openid, email, profile, and manage:project_data.
Let Claude or ChatGPT search, read and send your WhatsApp messages over MCP. OAuth sign-in.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Google Sheets, Docs, Slides, and Drive through a remote MCP server hosted on Cloudflare Workers, with OAuth authentication and Claude-native connect.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI agents to create Gmail drafts, send emails, and append content to Google Docs with OAuth-secured authentication.53 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to access and manage Google Workspace services such as Gmail, Drive, Docs, Sheets, Calendar, and Slides through the MCP protocol, with built-in OAuth 2.0 authentication and read/write tool support.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query read-only Google Search Console, GA4, Google Ads, and Workspace data through a single MCP endpoint, alongside a matching CLI. Sign-in happens once so the agent never sees Google tokens.MIT