Connect your AI assistant to AuthPI. Explore your identity configuration, set up a development application, and fix settings without leaving your conversation.
AuthPI MCP is a hosted server that lets your AI assistant work with your AuthPI account. The Model Context Protocol gives the assistant tools to read your configuration and make changes you authorize. You describe the task; the assistant uses the relevant tools.
Work on your application code and its identity settings in the same conversation.
Start by reading your setup. Grant write access when you want help creating resources or changing settings.
Add the server URL and sign in. There is no MCP server for you to install or run.
Ask about a specific account or application, or start by discovering what you have access to. Try these example prompts.
Discover accounts, choose an issuer, and inspect the settings your application is actually using.
“Show me the issuers in my Acme account. In the development issuer, list the OAuth clients and explain their callback URLs and scopes.”
Create an issuer and a public OAuth client for a browser or native app, with authorization-code PKCE. Write permission is required.
“In my Acme account, help me create a development issuer and a public SPA client for http://localhost:3000/callback. Show me the proposed configuration first.”
Read the current configuration, make a focused change, and verify the result. Version checks reject updates based on stale configuration.
“Inspect my development client. I moved the app to port 3001. Propose the callback change, keep the other URLs, and ask me before applying it.”
You can also inspect application organizations, users, and agents within an issuer, including their status and scopes. Explore the inspection tools →
Add AuthPI to a compatible AI assistant, sign in, and choose an account. AuthPI’s hosted MCP has been tested in ChatGPT and Codex.
Check compatibility with other clients ↓
New to AuthPI? Create an account first.
In your assistant’s MCP or connector settings, add a server named AuthPI with the URL https://mcp.authpi.com/mcp. Include the final /mcp.
Follow the AuthPI sign-in flow and approve the permissions you need. Your account membership must also permit those actions. You do not need to paste an organization API key into the assistant.
Ask “Which AuthPI accounts can I inspect?” Then choose an account and issuer before working on its resources. Try “Show me the issuers in my Acme account.”
Access, supported actions, and how this fits into your application.
ChatGPT and Codex have been tested with AuthPI’s hosted MCP. Other clients need remote Streamable HTTP, OAuth sign-in, and either Client ID Metadata Documents (CIMD) support or a registered OAuth client. AuthPI does not support Dynamic Client Registration. See the connection guide for requirements.
Yes. Approve read permissions without granting write permissions. The assistant can only perform actions allowed by both your consent and your current AuthPI account membership. Creating resources and changing settings require additional write access enabled by the service.
Yes, when your connection permits it. Ask the assistant to list your accounts, then choose one by name or ID. Each resource call carries the selected account and issuer context. A connection restricted to one account needs fresh authorization to select another.
It can create issuers and public SPA or native OAuth clients, and update supported issuer and client settings such as callback URLs, scopes, and session settings. Updates check the version that was read, so concurrent edits are reported instead of silently overwritten. Resource deletion, secret rotation, and client token-exchange policy changes are outside the tool set.
Tools return selected identity and configuration fields for resources you can access. They do not return passwords, client secrets, or verifier material. User and agent tools inspect records; they do not sign in as those identities.
Check your connection and discover accounts you can inspect.
whoamilist_accountsInspect configuration, available scopes, and identity settings.
list_issuersget_issuerInspect callbacks, grants, scopes, and client settings.
list_clientsget_clientInspect organizations within a chosen issuer.
list_organizationsget_organizationInspect identity records, status, and granted scopes.
list_usersget_userlist_agentsget_agentCreate issuers and public clients; update supported issuer and client settings with write permission.
create_issuercreate_clientupdate_issuerupdate_clientYes. This hosted server manages your resources in AuthPI. For an MCP server that exposes your own services, use AuthPI to authenticate your users and protect your API. Start with the MCP authorization guide.
Connect your assistant and ask it to show you around your account.