Descope MCP Server ## Introduction The Descope Model Context Protocol (MCP) server. Exposed over MCP by the descope mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

• 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

Configuration

You will need 2 environment variables: DESCOPE_PROJECT_ID, DESCOPE_MANAGEMENT_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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:

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Descope'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's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the descope mcp server does with a few real requests.