Skip to main content
Glama
TalissonFV

MCP User Management Server

by TalissonFV
README.md
# MCP Test Project

This is a simple user management service built with Node.js, TypeScript, and the Model Context Protocol (MCP).

## Prerequisites

- Node.js
- npm

## Getting Started

1.  **Clone the repository:**
    ```bash
    git clone <repository-url>
    ```
2.  **Install dependencies:**
    ```bash
    npm install
    ```
3.  **Build the project:**
    ```bash
    npm run server:build
    ```
4.  **Run the server in development mode:**
    ```bash
    npm run server:dev
    ```

## Available Scripts

- `npm test`: Runs the test suite (currently empty).
- `npm run server:build`: Compiles the TypeScript code to JavaScript.
- `npm run server:build:watch`: Compiles the TypeScript code in watch mode.
- `npm run server:dev`: Runs the server in development mode using `tsx`.
- `npm run server:dev:watch`: Runs the server in development mode with watch mode enabled.
- `npm run server:inspect`: Inspects the server using the MCP inspector.

## Project Structure

```
.
├── build/              # Compiled JavaScript files
├── node_modules/       # Project dependencies
├── src/                # TypeScript source code
│   ├── data/
│   │   └── users.json  # User data
│   └── server.ts       # MCP server implementation
├── package.json        # Project metadata and dependencies
├── tsconfig.json       # TypeScript configuration
└── ...
```

## API

The server exposes the following functionalities through the Model Context Protocol:

### Resources

- **`get-users` (`users://all`)**: Retrieves a list of all users.

### Tools

- **`create-user`**: Creates a new user with the following parameters:
  - `name` (string)
  - `email` (string)
  - `password` (string)
  - `address` (string)
  - `phone` (string)

TDQS

C2.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (create-user), and with only one tool, consistency is inherently perfect as there are no other names to deviate from this pattern.

Tool Count2/5

A server named 'User Management Server' with only one tool (create-user) is severely under-scoped, as user management typically requires at least get, update, delete, and list operations. This single tool feels incomplete and inadequate for the domain.

Completeness1/5

The tool surface is extremely incomplete for user management, lacking essential operations like retrieving, updating, deleting, or listing users. Agents will be unable to perform basic user management tasks beyond creation, leading to frequent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues