descope-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DESCOPE_PROJECT_ID | Yes | Your Descope Project ID from app.descope.com/settings/project | |
| DESCOPE_MANAGEMENT_KEY | Yes | Your Descope Management Key from app.descope.com/settings/company/managementkeys |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-auditsC | Search Descope project audit logs |
| search-usersC | Search for users in Descope project |
| create-userC | Create a new user in Descope project |
| invite-userC | Create and invite a new user to the Descope project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.