Skip to main content
Glama
descope-mcp-server

descope-mcp-server

Official

Descope MCP Server

Introduction

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.

Related MCP server: Dify Management MCP

Available Tools

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

Requirements

Before proceeding, make sure you have the following:

To confirm your Node.js installation, run:

node --version  # Expected output: v18.0.0 or later

Setup Instructions

Installing via Smithery

To install Descope MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @descope-sample-apps/descope-mcp-server --client claude

Manual Installation

  1. Clone the repository:

    git clone https://github.com/descope-sample-apps/descope-mcp-server.git
    cd descope-mcp-server
  2. Install the necessary dependencies:

    npm install
  3. Build the project:

    npm run build

Configuration

1. Configure Claude Desktop to recognize the Descope MCP server

To locate the claude_desktop_config.json file, open the Claude Desktop app and enable Developer Mode from the top-left menu bar.

Once enabled, go to Settings (also in the top-left menu), navigate to the Developer section, and click the Edit Config button to access and edit claude_desktop_config.json.

Alternatively, to open the configuration file via terminal:

On macOS:

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows:

code %APPDATA%\Claude\claude_desktop_config.json

2. Add the Descope server configuration:

{
  "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"
      }
    }
  }
}

Replace your-descope-project-id-here and your-descope-management-key-here with your actual Descope Project ID and Management Key from app.descope.com/settings/project and app.descope.com/settings/company/managementkeys.

3. Restart Claude Desktop

To apply the changes:

  1. Fully quit Claude Desktop (ensure it's not just minimized).

  2. Relaunch Claude Desktop.

  3. Check for the 🔌 icon to confirm the Descope server is connected.

Claude Desktop with Descope MCP Server x5

Running the server

First, build the project:

npm run build

1. Running the server on stdio

npm run start:stdio

2. Running the server on SSE

npm run start:sse

Available Tools

4 tools
create-userC

Create a new user in Descope project

Inputs: loginId (required), additionalLoginIds, email, verifiedEmail, +11 more.

invite-userC

Create and invite a new user to the Descope project

Inputs: loginId (required), additionalLoginIds, email, verifiedEmail, +16 more.

search-auditsC

Search Descope project audit logs

Inputs: loginIds, actions, excludedActions, tenants, +5 more.

search-usersC

Search for users in Descope project

Inputs: text, emails, phones, statuses, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 4 tools

    Disambiguation2/5

    The tools 'create-user' and 'invite-user' have significant overlap in purpose, as both involve creating new users, which could cause confusion for an agent. The other tools target distinct resources (audits vs. users), but the core user creation ambiguity is problematic.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with hyphens (e.g., create-user, search-audits), making them predictable and readable. There are no deviations in naming style across the set.

    Tool Count3/5

    With only 4 tools, the set feels thin for a user management and audit domain, potentially lacking operations like update-user, delete-user, or get-user. However, it covers basic creation and search functions, placing it in a borderline range.

    Completeness2/5

    For a user management server, there are significant gaps: no update, delete, or get operations for users, and audit functionality is limited to search only. This incomplete surface will likely cause agent failures in handling full user lifecycles.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers