MCP_CreateUser
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-userC | Create a new user in the database |
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 1 tool
There is only one tool, so there is no possibility of confusion or overlap with other tools. The single tool's purpose is clearly stated.
The tool name 'create-user' follows a clear verb-object convention. With only one tool, there are no inconsistent naming patterns to detract from coherence.
One tool is purpose-aligned for a server named MCP_CreateUser, but it still feels thin compared to typical 3-15 tool servers. There is no surrounding surface for related operations.
Only creation is exposed; there is no get, list, update, or delete for users. Any workflow that needs to verify, retrieve, or manage the created user will hit a dead end, making the surface significantly incomplete.