clue2app-user-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for SSE transport (default: 8080) | 8080 |
| COORDINATOR_URL | Yes | The base URL of the coordinator service (e.g., http://coordinator.control.svc.cluster.local) | |
| COORDINATOR_TOKEN | No | Bearer token for coordinator authentication (required for stdio transport, ignored for SSE transport) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_usersB | List users, optionally filtered by search query or project membership. |
| get_userB | Fetch a single user record by id. |
| disable_userA | Disable a user account. Requires SYSTEM token. Records the given reason for audit. |
| enable_userB | Re-enable a previously disabled user account. Requires SYSTEM token. |
| resolve_duplicate_usersA | Merge duplicate_ids into primary_id, keeping primary_id as the surviving user. Requires SYSTEM token. |
| list_user_membershipsB | List every project a user belongs to, with their role on each. |
| grant_roleA | Grant a user a role on a project. Requires SYSTEM or ACCOUNT_ADMIN token. |
| revoke_roleA | Revoke a user's role on a project. Requires SYSTEM or ACCOUNT_ADMIN token. |
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 8 tools
Each tool has a clearly distinct purpose: disabling, enabling, fetching, granting roles, listing memberships, listing users, resolving duplicates, and revoking roles. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., disable_user, grant_role). Naming is predictable and uniform.
8 tools is well-scoped for user management, covering core operations without unnecessary bloat.
The set covers enable/disable, role management, and listing, but lacks create_user and delete_user, which are minor gaps for a user management server.