Table of Contents
Modern development doesn’t happen in a browser anymore.
It happens in IDEs, terminals, code review tools, and increasingly, inside conversations with AI assistants. But documentation has lagged behind: fragmented across sites, sidebars, changelogs, GitHub repos, and mental bookmarks.
Today, we’re doing our part to help fix that.
We’re excited to announce the Descope Docs MCP Server: a hosted MCP server that gives AI agents and MCP-compatible tools direct, structured access to Descope’s product knowledge right where developers already work.
One predictable interface for Descope knowledge
The Descope Docs MCP Server consolidates Descope documentation, reference material, and public knowledge behind a single MCP endpoint.
Instead of:
Searching docs manually
Copy-pasting snippets into chat
Guessing which page contains the answer
Or hoping your AI assistant “remembers” something correctly
Your MCP client can now just ask Descope directly.
The server is hosted, read-only, and requires no setup beyond adding a URL: https://docs-mcp.descope.com/mcp
There’s nothing to install, no npm package to manage, and no auth required. You just add the URL to your MCP client—whether that’s Cursor, VS Code, Claude Desktop, Windsurf, ChatGPT, or a custom MCP host—and restart.
From that point on, Descope knowledge is always available where you work. Once connected, any MCP-aware AI assistant can reliably answer Descope-related questions using up-to-date source material.
You can find more information about our server and how to set it up in specific IDEs and MCP clients on our docs page.
Example: Adding auth to a Next.js app
To show what the Descope Docs MCP Server unlocks in practice, we recorded a short walkthrough demonstrating how to use the MCP server from an AI assistant to add authentication to a Next.js app in minutes.
In the video, we:
Connect the Descope Docs MCP Server to Cursor
Tell it to add auth and a user profile widget to a Next.js application in natural language
Let the assistant pull the right Descope SDK APIs and examples
Implement sign-in (with Descope Flows), session management, and delegated identity admin without opening the docs site once
This is the core promise of the Descope Docs MCP Server: from question to working auth flow, entirely in your development environment.
Descope Docs MCP Server tools
The Descope Docs MCP Server exposes two read-only tools that your MCP client will automatically choose between.
Ask a question about Descope
Tool: ask-question-about-descope
This is your “talk to a Descope expert” entry point. Use it for:
Troubleshooting errors and misconfigurations
Understanding product behavior and edge cases
Architectural and multi-step design questions
Conceptual explanations (auth flows, roles, tenants, MCP, etc.)
You ask a natural-language question; the tool retrieves relevant context and produces a grounded, complete answer.
Search Descope documentation
Tool: search-descope-docs
This tool performs semantic search across Descope documentation and other public sources (including reference content and GitHub). Use it when you want:
Direct excerpts from docs
Supporting references for an answer
A way to explore what exists before going deeper
Your AI assistant may use this tool on its own or combine it with the question-answering tool in the same interaction.
How AI assistants use the Docs MCP Server
You don’t need to manually pick which of the two tools to use. When your prompt is related to Descope, MCP-aware assistants typically follow a progressive discovery flow:
Search first: Use
search-descope-docsto locate relevant concepts, APIs, or error messages.Synthesize: Use
ask-question-about-descopeto produce a complete, contextual answer grounded in retrieved docs.Iterate: Refine, follow up, or zoom in on specific SDKs, frameworks, or flows.
This results in accurate answers without hunting through sidebars or guessing page paths.
Descope Docs MCP Server use cases
The Docs MCP Server works especially well for the following use cases:
Troubleshooting
“Why am I getting
Invalid session tokenwhen validating a JWT?”“Magic link works in dev but fails in prod—what should I check?”
“How do I fix CORS errors when embedding a Descope flow?”
How-to and setup
“How do I add Google OAuth to my Descope flow?”
“What’s the backend API to create a user with the Management API?”
“How do I validate a Descope JWT in a Lambda authorizer?”
Architecture and design
“Design a Next.js app with protected routes and admin-only access.”
“How should I handle multi-tenant role checks using Descope?”
“How do I implement step-up authentication for sensitive actions?”
MCP and agents
“How do I secure my own MCP server with Descope?”
“What scopes do I need for tool-level access control?”
Because the answers are grounded in real documentation, the server is safe to use in open-ended, exploratory conversations.
Powered by Inkeep + RAG
Under the hood, the Docs MCP Server is powered by Inkeep, which provides semantic search and AI-powered documentation Q&A using retrieval-augmented generation (RAG). That means:
Questions are grounded in real Descope documentation
Answers are based on retrieved sources, not guesswork
Long or architectural questions are handled holistically
The system stays current as docs evolve
Rather than exposing raw pages and leaving the rest to the model, the server pairs search + synthesis, optimized specifically for developer support workflows.
Get started
The Descope Docs MCP Server gives simple, predictable access to Descope documentation through the MCP protocol. Visit our docs page to learn more or just add the Descope Docs MCP Server to your MCP configuration with this URL: https://docs-mcp.descope.com/mcp
Then start asking real questions. Work with it to debug flows, design architectures, and explore features without leaving your editor or chat.
