Authorized clients

Authentication answers who the user is. The client registry answers which AI tool is connecting. Descope's policy only allows registered clients to start an OAuth flow — Cursor isn't on that list, so it never gets to the login step.

DocsClient registration ↗

Section 1 · MCP server auth

Clients authenticate to Descope, then connect to loan-ops-mcp with a scoped JWT. The server validates every call; tools pull downstream credentials from the Connections Vault.

Step 3 — Claude, ChatGPT, and the Custom Agent are registered OAuth clients and authenticate to Descope. Cursor is not registered and is blocked before it ever reaches the server.

1 / 4

Client auth → Descope · authorized call

SSO / connection token → downstream credential

Unregistered or unauthenticated (blocked)

Descope Console·Settings/Authorized clients

4 registered clients

Only these client IDs can initiate an authorization flow for the loan-ops-mcp tenant.

Client	Client ID	Status	Created	Owner	Tags
Claude Desktop	client_2NkXm7Pq…wf3a	verified	2026-02-14	kevin@northwind.com	mcp-clientanthropicdesktop-agent
AgentCore Account Copilot	client_AgC0re8x…u41q	verified	2026-03-04	priya@northwind.com	ai-agentaccount-copilothubspot
n8n Nightly Sweep	client_n8nBatch…7p2m	verified	2026-01-22	daniel@northwind.com	workflow-agentbatchn8n
support-triage-mcp	client_SupTri42…b9rs	unverified	2026-03-22	maria@northwind.com	mcp-clientinternaltriage-agent