Descope MCP Server

Descope Python SDK

Local serverstdioPython

What is the Descope MCP server?

Descope MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Descope Python SDK.

What you get

The Descope SDK for python provides convenient access to the Descope user management and authentication API for a backend written in python. You can read more on the Descope Website.

Setting it up

The server ships on PyPI as descope, 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.

What the assistant can call

Once Descope is connected, these are the calls the assistant has available:

  • OAuth — Users can authenticate using their social logins, using the OAuth protocol. Configure your OAuth settings on the [Descope
  • Passwords — The user can also authenticate with a password, though it's recommended to prefer passwordless authentication methods if possible. Sign up requires
  • History — You can get the current session user history. The request requires a valid refresh token
  • Setup — To use the management API you'll need a Management Key along with your Project ID. Create one in the [Descope

Configuration and credentials

You will need 3 environment variables: DESCOPE_AUTH_MANAGEMENT_KEY, 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.

The SDK supports Python 3.9 and above.

Before you rely on it

  • 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.

Choosing this one

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 — OAuth, Passwords, History and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Descope; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
OAuthUsers can authenticate using their social logins, using the OAuth protocol. Configure your OAuth settings on the [Descope console](https://app.descope.com/settings/authentication/social). To start a flow call:
PasswordsThe user can also authenticate with a password, though it's recommended to prefer passwordless authentication methods if possible. Sign up requires the caller to provide a valid password that meets all the requirements c
HistoryYou can get the current session user history. The request requires a valid refresh token.
SetupTo use the management API you'll need a Management Key along with your Project ID. Create one in the [Descope Console](https://app.descope.com/settings/company/managementkeys).

How to install the Descope MCP server

{
  "mcpServers": {
    "descope-1": {
      "command": "uvx",
      "args": ["descope"],
      "env": {
        "DESCOPE_AUTH_MANAGEMENT_KEY": "your-value",
        "DESCOPE_PROJECT_ID": "your-value",
        "DESCOPE_MANAGEMENT_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

The SDK supports Python 3.9 and above.

VariableDescriptionRequired
DESCOPE_AUTH_MANAGEMENT_KEYCredential the server authenticates with.Yes
DESCOPE_PROJECT_IDConfiguration value read at startup.Optional
DESCOPE_MANAGEMENT_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Descope to OAuth.
  • Use Descope to Passwords.
  • Use Descope to History.

Frequently asked questions

It connects Descope to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (OAuth, Passwords, History, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Descope directly.