---
title: "Discover Oidc Endpoints"
method: POST
path: "/api/v1/mcp_servers/discover_oidc"
tags: ["MCP Servers"]
---

# Discover Oidc Endpoints

`POST /api/v1/mcp_servers/discover_oidc`

DiscoverOIDCEndpoints fetches the OpenID Connect discovery document for an issuer
 and returns the authorization, token, and supported scopes.

## Request body

- C1ApiAiGovernanceV1MCPServerServiceDiscoverOIDCEndpointsRequest — MCPServerServiceDiscoverOIDCEndpointsRequest fetches the OpenID Connect discovery document for a given issuer URL.
  - `issuerUrl` string — The issuer URL (e.g. "https://accounts.google.com"). The server appends /.well-known/openid-configuration to this URL.

## Response `200`

MCPServerServiceDiscoverOIDCEndpointsResponse returns the discovered OAuth2 endpoints.

- C1ApiAiGovernanceV1MCPServerServiceDiscoverOIDCEndpointsResponse — MCPServerServiceDiscoverOIDCEndpointsResponse returns the discovered OAuth2 endpoints.
  - `authorizationEndpoint` string — The authorization endpoint URL.
  - `codeChallengeMethodsSupported` string[], nullable — PKCE code challenge methods supported by the authorization server (RFC 8414). Typical values: "plain", "S256". Empty when the discovery doc omits this field. The frontend should pass the array back unchanged on save so the backend can persist it on the connector and skip per-flow re-discovery.
  - `scopesSupported` string[], nullable — Scopes supported by the authorization server.
  - `tokenEndpoint` string — The token endpoint URL.

---

[API](https://skmtc.net/conductorone/apis/c1-api.md) · [All operations](https://skmtc.net/conductorone/apis/c1-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/conductorone/c1-api/revisions/f2cf3228f366/schema)