Skip to main content
POST
/
v1
/
integrations
/
connections
/
custom-mcp
/
discover
Pre-check a custom MCP server's OAuth/DCR support
curl --request POST \
  --url https://api-sandbox.featherhq.com/v1/integrations/connections/custom-mcp/discover \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "server_url": "<string>",
  "transport": "<string>"
}
'
{
  "supports_dcr": true,
  "authorize_url": "<string>",
  "token_url": "<string>",
  "scopes": [
    "<string>"
  ]
}

Authorizations

​
x-api-key
string
header
required

Body

application/json

Body for POST /v1/integrations/connections/custom-mcp/discover.

A read-only pre-check (no DB row) so the connect UI can detect whether a server supports OAuth Dynamic Client Registration before asking for a client_id. transport is accepted for symmetry with the connect body but is advisory — discovery probes well-known HTTP endpoints transport-agnostically.

​
server_url
string
required
​
transport
string | null

Response

Successful Response

Returned by POST /v1/integrations/connections/custom-mcp/discover.

supports_dcr is the signal the UI needs: True ⇒ hide the manual client_id fields (the server advertises an RFC 7591 registration endpoint); False ⇒ no discoverable metadata, so the user must supply a client_id.

​
supports_dcr
boolean
required
​
authorize_url
string | null
​
token_url
string | null
​
scopes
string[]