Discover and register an OAuth provider
Auto-discovers an OAuth provider’s metadata from an MCP server URL and registers it for your organization. Idempotent: the same provider_slug and mcp_server_url returns the existing provider (200). Reusing a provider_slug with a different mcp_server_url returns 400.
Authorizations
LangSmith API key (lsv2_...).
Body
MCP server discovery details
Custom callback URLs registered with the MCP authorization server via dynamic client registration so headless flows can redirect to them. The full set is registered when the provider is created and cannot be changed afterward — DCR has no update path, so re-creating the provider is required to change them. Omit the field or send an empty list when no custom callbacks are needed.
"https://tools.langchain.com/mcp/slack"
Response
OK
Callback URLs permitted as redirect_uri in headless auth sessions.
"https://github.com/login/oauth/authorize"
Extra static query parameters appended to the authorization URL.
"Iv1.0a1b2c3d4e5f6a7b"
PKCE challenge method; null when PKCE is unused.
"S256"
"2026-01-15T09:30:00Z"
"1a2b3c4d-5e6f-7081-92a3-b4c5d6e7f809"
True when registered via OAuth dynamic client registration.
false
Set when the provider was discovered from an MCP server.
"GitHub"
"7f8e9d0c-1b2a-3948-5766-8594a3b2c1d0"
"github-oauth-provider"
Provider family, e.g. oauth2 or mcp.
"oauth2"
"client_secret_post"
"https://github.com/login/oauth/access_token"
"2026-01-15T09:30:00Z"
Whether the provider uses PKCE in the authorization-code flow.
true

