Compatible with every major AI agent and IDE
What is the Descope (Auth Platform) MCP Server?
Connect Descope to your AI agent to manage and test user authentication flows through natural conversation. Descope is a drag-and-drop authentication and user management platform for any application.
What you can do
- OTP Authentication — Initiate and verify One-Time Passwords via Email, SMS, or Voice using tools like
auth_otp_signup_emailandauth_otp_verify_email. - Magic & Enchanted Links — Send secure sign-up/sign-in links and poll for session completion with
auth_magiclink_signup_emailorauth_enchantedlink_poll. - OAuth Integration — Start OAuth flows with providers like Google and exchange codes for active sessions using
auth_oauth_authorize. - Password Management — Handle traditional password-based sign-ups via
auth_password_signup. - Session Verification — Verify tokens and manage the authentication lifecycle directly from your workspace.
How it works
- Subscribe to this server
- Enter your Descope Project ID and optional Management Key
- Start managing your auth flows from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Developers — Test authentication logic and verify OTP/Magic Link flows without leaving the terminal or IDE.
- QA Engineers — Automate the verification of sign-up and sign-in processes through natural language queries.
- Product Managers — Quickly inspect how different auth providers and methods are configured in your project.
Built-in capabilities (33)
Poll for Enchanted Link session
Sign up a user via Enchanted Link
Verify an Enchanted Link token
Exchange an access key for a session JWT
Get public keys for session validation
Sign up or sign in a user via Magic Link
Verify a Magic Link token
Start OAuth flow
Exchange OAuth code for session
Sign in a user via Email OTP
Sign up a user via Email OTP
Sign up a user via SMS OTP
Sign up a user via Voice OTP
Verify an Email OTP
Verify an SMS OTP
Verify a Voice OTP
Reset a user password
Sign in a user with a password
Sign up a user with a password
Finish WebAuthn sign in
Start WebAuthn sign in
Finish WebAuthn sign up
Start WebAuthn sign up
Create a new access key (M2M)
Create a new permission
Create a new role
Create a new tenant
Create a new user
Delete a user
Load a user by login ID
Load all tenants
Search for users
Update an existing user
Why Cursor?
Cursor's Agent mode turns Descope (Auth Platform) into an in-editor superpower. Ask Cursor to generate code using live data from Descope (Auth Platform) and it fetches, processes, and writes. all in a single agentic loop. 33 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Descope (Auth Platform) in Cursor
Descope (Auth Platform) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Descope (Auth Platform) to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Descope (Auth Platform) in Cursor
The Descope (Auth Platform) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 33 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Descope (Auth Platform) for Cursor
Every tool call from Cursor to the Descope (Auth Platform) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I verify an email OTP code sent to a user?
Use the auth_otp_verify_email tool by providing the user's loginId (email) and the code they received. The agent will return the session details if the verification is successful.
Can I start a Google OAuth login flow using this server?
Yes. Use the auth_oauth_authorize tool with 'google' as the provider and specify your redirectURL. The agent will initiate the OAuth flow for you.
What is the purpose of the enchanted link polling tool?
The auth_enchantedlink_poll tool allows the agent to check the status of a pending enchanted link authentication using a pendingRef. It helps determine if the user has clicked the link and completed the session.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
NOAA Tides & Currents API
5 toolsMonitor tidal data — audit water levels and predictions via AI.

LibraryThing
4 toolsLook up books by ISBN, explore works, and check library coverage — a bibliographic intelligence tool for AI agents.

CommPeak
9 toolsEnable your AI agent to manage dialer campaigns, leads, and send SMS messages via the CommPeak API.

TF-IDF Vectorizer Engine
1 toolsExact Term Frequency-Inverse Document Frequency scores. Stop LLMs from guessing keyword relevance across massive corpuses.
