The Descope MCP Server allows you to interact with Descope's Management APIs to manage and retrieve project-related information. You can:
- Search audit logs: Retrieve audit log entries with filters for locations, action types, authentication methods, tenant IDs, and more
- Search users: Find user records with filters like roles, email addresses, phone numbers, login IDs, statuses, and tenant IDs
- Create users: Add new users to your Descope project, specifying details like email, phone, roles, and custom attributes
- Invite users: Create and invite new users to your project with customizable invitation options
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.
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:
- 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:
Setup Instructions
Installing via Smithery
To install Descope MCP Server for Claude Desktop automatically via Smithery:
Manual Installation
- Clone the repository:
- Install the necessary dependencies:
- Build the project:
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:
On Windows:
2. Add the Descope server configuration:
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:
- Fully quit Claude Desktop (ensure it's not just minimized).
- Relaunch Claude Desktop.
- Check for the 🔌 icon to confirm the Descope server is connected.
Running the server
First, build the project:
1. Running the server on stdio
2. Running the server on SSE
local-only server
The server can only run on the client's local machine because it depends on local resources.
Interact with Descope's Management APIs to manage users, audit, and more.
Related Resources
Related MCP Servers
- -security-license-qualityProvides an interface to manage publishers, upgrade profiles, access policies, and steering for Netskope's Network Private Access (NPA) API.Last updated -TypeScript
- AsecurityFlicenseAqualityProvides tools for managing Netskope infrastructure, policies, and steering configurations via the Model Context Protocol.Last updated -5002TypeScript
- -securityFlicense-qualityIntegrates with the Ghost Admin API to allow programmatic management of Ghost CMS features, including posts, pages, tags, authors, members, and image uploads, providing efficient content management capabilities.Last updated -112TypeScript
- AsecurityAlicenseAqualityThis server provides a convenient API for interacting with Azure DevOps services, enabling AI assistants and other tools to manage work items, code repositories, boards, sprints, and more. Built with the Model Context Protocol, it provides a standardized interface for communicating with Azure DevOpsLast updated -964343TypeScriptMIT License