mcp-oauth-providers
OAuth provider registrations for MCP servers — the credential-issuer records that let external MCP clients authenticate to a Celigo MCP server.
REST API: MCP OAuth Providers
celigo mcp-oauth-providers <subcommand> [args] [flags]Supports all global flags.
Subcommands
list
List all MCP OAuth providers.
get <id>
Fetch one MCP OAuth provider by ID.
create
Create an MCP OAuth provider from JSON (stdin or --file).
update <id>
Full-replace PUT from JSON (stdin or --file).
set <id> key=value …
Refused on this group — credentials are masked. Use update.
delete <id>
Delete an MCP OAuth provider by ID.
celigo mcp-oauth-providers list
List all MCP OAuth providers on the account.
Signature
celigo mcp-oauth-providers listArguments
None.
Flags
--fields <spec>
string
default
Fields to request per row. default returns _id, name, and the table columns; all returns complete documents; a comma-separated list requests specific fields. See field projection.
--limit <n>
integer
—
Return at most <n> rows, fetching a single page.
Example
Corresponds to: GET /v1/mcpoauthproviders (operationId: listMcpOauthProviders)
celigo mcp-oauth-providers get
Fetch one MCP OAuth provider by ID.
Signature
Arguments
<id>
string
Yes
MCP OAuth provider ID.
Example
Corresponds to: GET /v1/mcpoauthproviders/{_id} (operationId: getMcpOauthProviderById)
celigo mcp-oauth-providers create
Create an MCP OAuth provider from a JSON body. Reads from stdin by default, or from a file with --file.
Signature
Flags
-f, --file <path>
string
stdin
Read the JSON body from a file instead of stdin (- also means stdin).
Request body
Reads JSON. See the POST /v1/mcpoauthproviders schema for the full payload shape.
Example
Corresponds to: POST /v1/mcpoauthproviders (operationId: createMcpOauthProvider)
celigo mcp-oauth-providers update
Full replace of an MCP OAuth provider from a JSON body. Omitted fields are erased. Reads from stdin by default, or from a file with --file.
⚠️
updatereplaces the entire provider. Any field you omit is erased.GETthe current record first, modify it, thenPUTthe complete object back.
GET masks the provider's encrypted fields as ******. If you edit that response and submit it unchanged, update refuses the payload, names each masked path it found, and exits without calling the API — submitting the placeholders would overwrite the real credentials. Replace each masked value with the actual secret, use "" to clear it, or pass --force to submit the payload as written.
Signature
Arguments
<id>
string
Yes
MCP OAuth provider ID.
Flags
-f, --file <path>
string
stdin
Read the JSON body from a file instead of stdin (- also means stdin).
--force
boolean
false
Submit even if the body contains masked credential values (***) copied from a GET.
Request body
Reads JSON. See the PUT /v1/mcpoauthproviders/{_id} schema for the full payload shape.
Example
Corresponds to: PUT /v1/mcpoauthproviders/{_id} (operationId: updateMcpOauthProvider)
celigo mcp-oauth-providers set
⚠️
setrefuses every field on this group, by design. The API masksclientSecretas******on read, so theGET→ modify →PUTthatsetwould use overwrites the stored secret with the mask. Rather than destroy the credential,setfails with a message naming the field and directing you toupdate. Useupdatewith the real credential values.
Signature
Arguments
<id>
string
Yes
MCP OAuth provider ID.
[assignments...]
key=value pairs
Yes
One or more field assignments. Every assignment is refused — see the callout above.
Behavior
set chooses one of three strategies per resource group. On groups with a PATCH whitelist, whitelisted fields apply atomically. On other groups it round-trips GET → modify → PUT. MCP OAuth providers are a credential-masked group with no whitelist, so neither path is safe and the command errors instead:
Connections and iClients carry the same guard, but both have a PATCH whitelist, so a whitelisted field still succeeds there.
Example
celigo mcp-oauth-providers delete
Delete an MCP OAuth provider by ID.
⚠️ Deleting an OAuth provider cannot be undone. Any MCP server that references this provider for client authentication will stop authenticating those clients.
Signature
Arguments
<id>
string
Yes
MCP OAuth provider ID.
Flags
-y, --yes
boolean
false
Skip confirmation.
Example
Corresponds to: DELETE /v1/mcpoauthproviders/{_id} (operationId: deleteMcpOauthProvider)
Related
mcp-servers — MCP server resources that reference an OAuth provider for client authentication.
Last updated
Was this helpful?