You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A customer building a companion CLI/SDK for their MCP server (already using Scalekit OAuth) asked about best practices for CLI-specific PKCE flows and dynamic client registration (DCR). Scalekit does not currently document a recommended approach for the MCP client side of this integration (Pylon #658).
Customer question
I was able to integrate your OAuth flow for my MCP server, and now I'm building a companion SDK/CLI that will access the same MCP server endpoints. Do you have any best practices or utils to instrument the SDK/CLI to perform dynamic client registration?
Support response
Pointed to the mcp-jam reference implementation as the closest available resource. Scalekit noted it does not have native utilities for the MCP client side.
Summary
A customer building a companion CLI/SDK for their MCP server (already using Scalekit OAuth) asked about best practices for CLI-specific PKCE flows and dynamic client registration (DCR). Scalekit does not currently document a recommended approach for the MCP client side of this integration (Pylon #658).
Customer question
Support response
Pointed to the mcp-jam reference implementation as the closest available resource. Scalekit noted it does not have native utilities for the MCP client side.
Documentation gap
The docs should cover:
localhost:{port}or loopback addresses), including Scalekit's wildcard port matching for localhost (see also GH docs: add MCP auth troubleshooting — localhost redirect URI and CIMD/DCR fallback #586)Related issues
References