descope -stdio

This Descope MCP Server provides an interface to Descope's Management APIs, enabling you to search and retrieve project-related information via the MCP protocol. The server exposes a set of tools you can invoke through MCP-compatible clients (such as Claude Desktop) to perform common tasks without direct API interaction. The available tools include: search-audits (fetches up to 10 audit log entries for your Descope project), search-users (fetches up to 10 user records), create-user (creates a new user in your Descope project), and invite-user (sends an invitation to a new user). To use these tools, configure the MCP server in your client (e.g., Claude Desktop) with the provided command, arguments, and environment variables. Then issue tool commands like search-audits, search-users, create-user, and invite-user as part of your MCP session. The server handles authentication via the configured Descope Project ID and Management Key, and returns structured results that your client can display or process further.

Prerequisites:

• Node.js version 18 or later
• Git
• Access to a Descope Project ID and Management Key
• Optional: Claude Desktop (for interactive MCP usage)

Installation options:

1. Installing via Smithery (automated):

   • Run:

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

   • This installs and configures the MCP server to work with Claude Desktop.

2. Manual installation:

   • Clone the repository:

     git clone https://github.com/descope-sample-apps/descope-mcp-server.git
     cd descope-mcp-server
     

   • Install dependencies:

     npm install
     

   • Build the project (if a build step is required by the server):

     npm run build
     

After installation, configure the MCP server in your Claude Desktop or MCP client by providing the command, arguments, and environment variables as described in the mcp_config section.

Tips and notes:

• Ensure Developer Mode is enabled in Claude Desktop to access and edit claude_desktop_config.json.
• In your configuration, replace the placeholder DESCOPE_PROJECT_ID and DESCOPE_MANAGEMENT_KEY with your actual credentials from Descope.
• If you switch from stdio to SSE (server-sent events) or different transport modes, update the corresponding start commands (e.g., npm run start:stdio or npm run start:sse).
• After updating configuration, fully quit Claude Desktop and relaunch to establish a new MCP connection. Look for the connected status indicator (the 🔌 icon).
• Common issues often involve invalid credentials or incorrect project IDs. Double-check values in your Descope console and ensure they match what you place in env vars.
• The npm_package field in this document uses the package name as published for this MCP server; for this project, it is the Descope-sample apps MCP server package.