E-File Magic

MCP clients

Register an MCP client

Register public MCP client metadata only after an authorized operator enables MCP for the environment. A missing, invalid, or disabled MCP policy fails closed independently of private API rollout. Registration grants no account access.

POST
/oauth/register
Authentication
No access token required
Required scopes
See authentication requirements
Idempotency key
Not required

Request fields

6 fields
client_nameSee descriptionSee description

Required nonempty name, at most 80 bytes; no control characters or angle brackets.

redirect_urisSee descriptionSee description

Required 1–8 distinct URIs, at most 2048 bytes each: HTTPS, or HTTP on literal loopback 127.0.0.1/[::1]; no user information or fragment.

token_endpoint_auth_methodSee descriptionSee description

Optional; only none, the default, is accepted.

grant_typesSee descriptionSee description

Optional; defaults to authorization_code and refresh_token. Must include authorization_code; client_credentials is unavailable.

response_typesSee descriptionSee description

Optional; only ["code"], the default, is accepted.

scopeSee descriptionSee description

Optional space-separated supported preparation scopes. Filing submission is not a registration scope.

cURL request
curl --request POST '<origin from OAuth metadata>/oauth/register' \
  --header 'Content-Type: application/json' \
  --data-binary @request.json

Use the exact endpoint URL from your environment's metadata. Confidential client examples use client_secret_basic; public MCP clients use client_id without a secret.

Create request.json using the documented fields. Field descriptions are not sample values.