F
licenseNot graded
qualityD
maintenanceA user management MCP server that enables CRUD operations on users stored in a JSON file, with random user generation using Faker.
9
1
-
User Management MCP Server
Related Servers
Alternatives to User Management MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA testing server that demonstrates Model Context Protocol features, providing access to user data, todos, and system information through resources, tools for user management and calculations, and prompt templates for various analyses.4-
- AlicenseNot gradedqualityDmaintenanceA simple Model Context Protocol (MCP) server that allows LLMs to create and manage user entries in a JSON file system database.801MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact with user and task data through JSON-RPC, offering tools like user management, task creation, and search functionality.89-
- AlicenseBqualityBmaintenanceA Model Context Protocol server that provides tools to manage Keycloak users and realms, allowing you to create and delete users, list available realms, and view users in specific realms.413046MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables performing PostgreSQL database operations (create, read, update, delete) on User and Post entities through MCP tools.300MIT
TDQS
C2.9/5.0
Scored across 2 tools
Disambiguation1/5
The two tools have highly overlapping purposes: both create users. 'create-random-user' and 'create-user' differ only in the data source (fake vs. system), which is a subtle distinction that agents will likely confuse. This is a classic case of ambiguous tool boundaries.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern with hyphen-separated names. 'create-random-user' and 'create-user' are perfectly aligned in naming style, making them predictable and readable.
Tool Count2/5
With only 2 tools, the server feels severely under-scoped for a 'User Management' domain. A user management system typically requires at least CRUD operations (create, read, update, delete) and possibly list/search tools. This minimal set is inadequate for the implied purpose.
Completeness1/5
The tool surface is extremely incomplete for user management. There are no tools to retrieve, update, delete, or list users, creating significant gaps that will cause agent failures. Agents cannot perform basic user management workflows beyond creation.
Maintenance
ActivityInactive
ResponsivenessNo issues