ConnectCloud Developers

Register an OAuth client (dynamic client registration, no sign-in)

POST /api/hr/v1/oauth/register

Module: HR · operationId: registerOAuthClient · Tag: Auth · Auth: none

RFC 7591 registration for MCP clients (Claude Code, ChatGPT, Cursor …), which then connect to the portal's MCP server as a person or service account. Clients are public: no secret, token_endpoint_auth_method is always none, PKCE (S256) is required. client_name (1–100 characters) and 1–5 redirect_uris are needed: https URIs, or http on localhost, 127.0.0.1 or [::1] (any port at use time, RFC 8252), never with a fragment or user info. Other metadata is ignored. Errors follow RFC 7591 (invalid_redirect_uri, invalid_client_metadata). Rate limited per client (1 per second, bursts up to 5).

Request body

application/json (required)

  • client_name (string, required): (max length 100)
  • redirect_uris (array of string, required)

Example:

{
  "client_name": "Claude Code",
  "redirect_uris": [
    "http://127.0.0.1:3333/callback"
  ]
}

Responses

  • 201 Registered client (application/json)
  • 400 OAuth error (RFC 6749 §5.2, RFC 7591 §3.2.2) (application/json)
  • 429 Too many requests

Fields of the 201 answer:

  • client_id (string)
  • client_name (string)
  • grant_types (array of string)
  • redirect_uris (array of string)
  • response_types (array of string)
  • token_endpoint_auth_method (string): (one of none)

Example 201 answer:

{
  "client_id": "cco_EXAMPLEQ2xhdWRlQ29kZQ",
  "client_name": "Claude Code",
  "grant_types": [
    "authorization_code",
    "refresh_token"
  ],
  "redirect_uris": [
    "http://127.0.0.1:3333/callback"
  ],
  "response_types": [
    "code"
  ],
  "token_endpoint_auth_method": "none"
}

Example request

curl -X POST 'https://api.mbcom.cloud/api/hr/v1/oauth/register' \
  -H 'Content-Type: application/json' \
  --data '{"client_name":"Claude Code","redirect_uris":["http://127.0.0.1:3333/callback"]}'

View as Markdown · Interactive reference · OpenAPI