PropelAuth Integration MCP Server

Returns instructions for integrating PropelAuth in a backend framework such as Python, FastAPI, Django, Flask, Rust, Node, Go, Express, and .NET. Guidance includes installation and configuration, protecting API routes, and checking org membership and permissions. It is important to follow the instructions carefully to ensure a successful integration. Do not update the guidance argument unless the user explicitly requests it.

Returns instructions for integrating PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered, optionally with API calls; use the integrate_propelauth_fullstack tool for fullstack integration that uses server-side rendering). Guidance includes installation and configuration, creating access tokens, retrieving user or org information, logging users out, redirecting users to login, and more. It is important to follow the instructions carefully to ensure a successful integration. Do not update the guidance argument unless the user explicitly requests it

Returns instructions for integrating PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the integrate_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. Do not update the guidance argument unless the user explicitly requests it.

IMPORTANT: Do NOT fetch all guidances at once. Fetch the 'Backend Installation' guidance first, apply the necessary setup changes, and then fetch subsequent guidances (e.g., 'Redirect users after login', 'Backend Auth Middleware') sequentially as you implement each specific feature. Returns instructions for integrating PropelAuth via OAuth. Only use this tool when specifically instructed to by another tool or the user or if a PropelAuth SDK does not exist for the project's framework. Guidance includes instructions for the backend and frontend, including installation and configuration, creating access tokens, retrieving user or org information, logging users out, redirecting users to login, and more. It is important to follow the instructions carefully to ensure a successful integration.

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.

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.

Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the migrate_to_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. 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

Returns instructions for migrating users and organizations to PropelAuth from other auth providers, such as Clerk. Each guidance will include documentation from the other auth provider and PropelAuth.

Returns instructions and provides examples for using PropelAuth's backend APIs. Examples include APIs for users, organizations, Enterprise SSO (SAML/OIDC), API Keys, and Step Up MFA/2FA. Before using this tool, make sure you have installed PropelAuth's backend SDK for your framework (use the 'integrate_propelauth_backend' tool). If an SDK is not available for your framework, you can use the 'Other' option for the framework argument.

Returns instructions and provides examples for using PropelAuth's frontend APIs to create custom UIs to replace PropelAuth's hosted pages. Examples include login and signup pages, MFA flows, managing organizations, inviting, removing, or updating users in an organization, managing and creating API keys, updating the user's email, verifying MFA, the org member table, api key tables, updating user properties, updating org membership, and more. Before installing any component, make sure to use the 'Installation' guidance first. If instructed to build a login or signup related UI, use the 'LOGIN_AND_SIGNUP_INSTALLATION' guidance first.

Returns instructions and guidance on how to resolve common troubleshooting issues. Examples include debugging infinite redirects, third-party cookie issues, access tokens expiring, random logouts, CORS issues, 404 errors when using OAuth, incorrect API key errors, and incorrect verifier key errors.