"OpenID" matching MCP tools:

• migrate_to_propelauth_frontendA

  PropelAuth Integration MCP ServerA

  Returns instructions for migrating to PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered). Guidance includes migrating from several auth providers, such as Clerk or Auth0. Each guidance will include documentation from the auth provider and PropelAuth. It is important to follow the instructions carefully to ensure a successful integration. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc. CRITICAL: If the current implementation uses a traditional OAuth/OIDC flow (e.g., via express-openid-connect, passport-auth0, or similar backend-managed session libraries), you MUST select 'OAuth' as the framework, regardless of the frontend library (React/Vue/etc.). Only select 'React' or 'Javascript' if the current implementation uses a frontend-only SDK (like @auth0/auth0-react) or if using fullstack Next.js.

  ConnectorNo auth

• create_projectA

  MockbirdA

  Create a new mock REST API project. Returns {id, adminKey, baseUrl, resources[]}. SAVE the adminKey — it is required for admin operations (add_resource, custom_route, snapshots) and is shown only once. Presets seed a full backend: blog (posts/comments/authors), ecommerce (products/orders/customers/reviews), saas (users/teams/events), payments (Stripe-shaped sandbox: charges/refunds/subscriptions/customers + payment_intent create→confirm flow + /v1/balance — no keys), openai (ready OpenAI-compatible mock — chat completions incl. streaming SSE, embeddings with a real 1536-dim vector, models; point OPENAI_BASE_URL at {baseUrl}/v1). Omit preset for a starter project (one seeded "items" resource — live data immediately, reshape or delete it); use "blank" for a truly empty project you fill via add_resource or import_data. The mock API is then live at baseUrl: standard REST CRUD (GET/POST/PUT/PATCH/DELETE), CORS enabled, no auth needed. Every project also serves a mock OAuth2/OIDC provider at {baseUrl}/.well-known/openid-configuration (PKCE code flow, client_credentials, RS256 JWKS — any client_id works) for testing auth flows.

  ConnectorNo auth

• generate_filesA

  agent-ready-kitA

  Use this when delivering files to a paid customer (you must have their bundle_key) OR when a downstream agent wants the free starter files for a domain. **FREE TIER (no bundle_key)**: returns metadata + a `download_url` pointing at a streaming ZIP of the 2 starter files (robots.txt + llms.txt). DO NOT paste raw file contents into chat — the file bodies are NOT in the response. Render the download_url as a markdown link: `[Download free starter files (ZIP) →](url)`. **PAID TIER (valid bundle_key)**: returns the full surface — agent card, MCP server card, agent skills, WebMCP bridge, OAuth/OpenID discovery, API catalog — as inline file objects (chunked above 8KB). For pricing evaluation, call get_pricing_tiers and direct the user to /talk.

  ConnectorNo auth

• list_connected_channelsA

  TrezaA

  The YouTube channels, TikTok accounts, and Instagram accounts connected to this Treza account, with the ids a publishing node needs. A youtube-upload node needs a channelId, a tiktok-upload node needs an openId, and an instagram-upload node needs an igUserId; all come from here. Connecting a new one is done by a human under Settings, Connected accounts, and no tool can do it.

  ConnectorAPI key

• migrate_to_propelauth_backendA

  PropelAuth Integration MCP ServerA

  Returns instructions for migrating to PropelAuth in a backend framework such as Express, FastAPI, Go, and more; Guidance includes migrating from either Clerk or Auth0. Each guidance will include documentation from the auth provider and PropelAuth. It is important to follow the instructions carefully to ensure a successful integration. It is important to call each guidance individually to ensure a successful integration. IMPORTANT: The backend_framework choice depends on the current auth provider implementation, not just the language. Select 'OAuth' if the backend currently handles the login flow using redirects (e.g., uses express-openid-connect or passport). Select any other option only if the current backend is a pure API that validates JWTs without managing the redirect-based login session. This excludes fullstack Next.js implementations.

  ConnectorNo auth

• hodlxxi_get_openid_configurationA

  HODLXXI Read-OnlyA

  Return OpenID Connect discovery metadata: issuer, authorization and token endpoints, JWKS URI, grants, scopes, PKCE, and signing algorithms.

  ConnectorNo auth

• cronofy_get_userinfoA

  cronofyA

  Get the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info). API: GET /v1/userinfo.

  ConnectorNo auth

• verify_colony_handleA

  ProgenlyB

  Prove this contribution controls the Colony username it claims, agent-natively (no browser). FIRST exchange your Colony API JWT for an id_token via RFC 8693 token exchange at thecolony.ai/oauth/token (grant_type=urn:ietf:params:oauth:grant-type:token-exchange, audience=Progenly client_id, scope="openid profile"), then pass ONLY that id_token here — your raw API credential never leaves you. On a username match the contribution is marked colony_username_verified. Needs your participant_token (or owner_token).

  ConnectorNo auth