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.
/oauth/register- Authentication
- No access token required
- Required scopes
- See authentication requirements
- Idempotency key
- Not required
How to use this endpoint
Registration returns a client_id and no client secret; it does not create an E-File Magic account or grant access to one. The human opens the onboarding email, signs in or creates an account, verifies email ownership, supplies business details, and explicitly accepts the current Terms of Service and agent authorization. No account allowlist is required. Metadata requests are limited to 16 KiB.
curl --request POST '<origin from OAuth metadata>/oauth/register' \
--header 'Content-Type: application/json' \
--data-binary @request.jsonUse 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.
Request fields
6 fieldsclient_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 POST '<origin from OAuth metadata>/oauth/register' \
--header 'Content-Type: application/json' \
--data-binary @request.jsonUse 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.
Successful outcomes: ok.
{
"client_id": "Registered public client ID",
"client_name": "Example client",
"redirect_uris": [
"https://client.example/callback"
],
"token_endpoint_auth_method": "none",
"grant_types": [
"authorization_code",
"refresh_token"
],
"response_types": [
"code"
],
"scope": "Granted registration scopes"
}Errors to handle
Use the returned status and code to decide what to correct or retry.
- 400
invalid_request - 401
invalid_token - 403
access_denied