Connect a browser client
Authorize a remote MCP connector without sharing a personal key.
Configure the connector
In a client supporting remote Streamable HTTP MCP and OAuth, add a remote server using this URL:
https://mcp.alshival.ai/mcpChoose its sign-in or authenticate action. Client labels vary. Review the client name on the Alshival consent screen, select workspaces and keep write access off unless you need it.
Complete consent
Allow the selected access, return to the client and request project discovery. Denying consent leaves the connection unauthorized. A client that cannot complete OAuth should report the failure; it must not silently request broader access.
Verified browser flow
MCP Inspector completed registration, browser consent, connection and a project read against the public endpoint. This does not establish compatibility with every hosted connector or subscription plan.
Disconnect
Revoke the connected application in Security & sign-in. Removing a client-side connection alone is not a substitute for revoking its server grant.