Update README and OAuth response handling for improved user flow
This commit is contained in:
@@ -81,7 +81,7 @@ Use a dedicated public hostname such as `mcp.ryankegel.com` and terminate HTTPS
|
||||
|
||||
The MCP endpoint is `https://mcp.ryankegel.com/mcp`. The OAuth discovery and login endpoints share that hostname. The MCP allowed-host setting also prevents requests to unexpected hostnames.
|
||||
|
||||
5. In ChatGPT on the web, add a custom MCP server with that `/mcp` URL and choose OAuth authentication. The server supports Dynamic Client Registration (DCR). On the first authorization, sign in with `MCP_AUTH_USERNAME` and the password stored in `secrets/mcp_auth_password`, then approve the requested vault access.
|
||||
5. In ChatGPT on the web, add a custom MCP server with that `/mcp` URL and choose OAuth authentication. The server supports Dynamic Client Registration (DCR). On the first authorization, sign in with `MCP_AUTH_USERNAME` and the password stored in `secrets/mcp_auth_password`, approve the requested vault access, then click **Continue** to return to ChatGPT.
|
||||
|
||||
## Enable writes
|
||||
|
||||
|
||||
Reference in New Issue
Block a user