Skip to content

Commit 26447cc

Browse files
authored
docs: update BYOA article — new code sample link and dashboard screenshots (#751)
* docs: update BYOA article with new code sample link and dashboard screenshots * fix: swap misnamed BYOA screenshot files
1 parent 8237155 commit 26447cc

3 files changed

Lines changed: 4 additions & 4 deletions

File tree

127 KB
Loading
211 KB
Loading

src/content/docs/mcp/auth-methods/custom-auth.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -219,7 +219,9 @@ curl --location '{{env_url}}/api/v1/connections/{{connection_id}}/auth-requests/
219219
- Replace placeholders like `{{env_url}}`, `{{connection_id}}`, `{{login_request_id}}`, and `{{access_token}}` with actual values.
220220
- Only `sub` and `email` are required fields; all other properties are optional.
221221

222-
**Finding your `connection_id`:** Open **Dashboard > MCP Servers > [your server] > Advanced Configurations > Connection ID**. It starts with `conn_` and is distinct from the MCP server's resource ID (which starts with `res_`). Do not use the resource ID here.
222+
**Finding your `connection_id`:** Open **Dashboard > MCP Servers > [your server] > Configuration > Advanced Configuration > Connection ID**. It starts with `conn_` and is distinct from the MCP server's resource ID (which starts with `res_`). Do not use the resource ID here.
223+
224+
![MCP Server Advanced Configuration showing BYOA settings — Login Endpoint URL, Connection ID, User Info Post URL and Redirect URL](@/assets/docs/mcp/byoa-configuration.png)
223225

224226
**Using raw HTTP instead of the SDK:** Making direct HTTP calls to this endpoint is a fully supported alternative to using an SDK. If the SDK introduces transitive dependency conflicts in your project, use the cURL tab above for the equivalent request.
225227

@@ -252,6 +254,4 @@ curl --location '{{env_url}}/api/v1/connections/{{connection_id}}/auth-requests/
252254

253255
:::
254256

255-
**Download our sample MCP Server:** We have put together a simple MCP server that you can check out and run it locally to test the end to end functionality of a working MCP server complete with authentication and authorization. You can download and execute a sample MCP server implementation from <a href="https://github.com/scalekit-inc/mcp-auth-demos" target="_blank" rel="noopener">GitHub</a>.
256-
257-
**Try out the BYOA MCP server**: Scalekit provides a demo MCP server that shows how to implement your own auth integration. Clone the <a href="https://github.com/scalekit-inc/byoa-demo-mcp" target="_blank" rel="noopener">BYOA MCP server</a> to test end-to-end authentication in your environment.
257+
**Try out the BYOA MCP server**: Clone the <a href="https://github.com/scalekit-inc/mcp-auth-demos/tree/main/byoa-mcp-node" target="_blank" rel="noopener">byoa-mcp-node sample</a> — a working Node.js MCP server with a custom login page, Scalekit token validation, and custom claims flowing through to tool handlers. Follow the README to run it locally end-to-end.

0 commit comments

Comments
 (0)