The Descope Model Context Protocol (MCP) server provides an interface to interact with Descope's Management APIs, enabling the search and retrieval
The Descope Model Context Protocol (MCP) server provides an interface to interact with Descope's Management APIs, enabling the search and retrieval of project-related information. That is what the descope stdio mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 4 tools. What each one is for:
search-audits — Retrieves up to 10 audit log entries from your Descope projectsearch-users — Retrieves up to 10 user records from your Descope projectcreate-user — Creates a new user in your Descope projectinvite-user — Invites a new user to your Descope projectConfiguration is passed through the environment: DESCOPE_PROJECT_ID, DESCOPE_MANAGEMENT_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Before proceeding, make sure you have the following: - Node.js (version 18 or later) - Claude Desktop installed on your system - A valid Descope Project ID and Management Key - Git installed To confirm your Node.js installation, run:
The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Descope Stdio's toolset — search-audits, search-users, create-user and 1 more — is a fair guide to whether it matches your workflow. It is maintained by descope-sample-apps; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Descope Stdio's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| search-audits | Retrieves up to 10 audit log entries from your Descope project. |
| search-users | Retrieves up to 10 user records from your Descope project. |
| create-user | Creates a new user in your Descope project. |
| invite-user | Invites a new user to your Descope project. |
{
"mcpServers": {
"descope": {
"command": "node",
"args": ["/path/to/descope-mcp-server/build/index.js"],
"env": {
"DESCOPE_PROJECT_ID": "your-descope-project-id-here",
"DESCOPE_MANAGEMENT_KEY": "your-descope-management-key-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
Before proceeding, make sure you have the following: - Node.js (version 18 or later) - Claude Desktop installed on your system - A valid Descope Project ID and Management Key - Git installed To confirm your Node.js installation, run:
| Variable | Description | Required |
|---|---|---|
| DESCOPE_PROJECT_ID | Configuration value read at startup. | Optional |
| DESCOPE_MANAGEMENT_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.