Gestion MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Puerto HTTP cuando se usa transporte SSE | 3000 |
| BACKEND_URL | No | URL base de la API REST del backend | http://localhost:8080 |
| MCP_TRANSPORT | No | Modo de transporte: stdio o sse/http | stdio |
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 |
|---|---|
| loginA | Authenticate with the backend API using email and password. Stores the JWT token for subsequent authenticated requests. Call this first before any other tool that requires authentication. |
| get_meA | Get the current authenticated user's session information. Requires prior login via the 'login' tool. |
| logoutA | Clear the stored JWT token and end the current session. |
| list_personasA | List people from the backend with optional search, pagination, and sorting. Requires authentication (ADMIN, MANAGER, or USER role). |
| get_personaA | Get a single person by their ID. Requires authentication. |
| create_personaA | Create a new person in the system. Requires ADMIN or MANAGER role. |
| update_personaA | Update an existing person by ID. Only the fields provided will be updated. Requires ADMIN or MANAGER role. |
| delete_personaB | Delete a person by ID. Requires ADMIN role only. |
| list_usuariosA | List users from the backend with optional filters, pagination, and sorting. Requires ADMIN or MANAGER role. |
| get_usuario_by_emailA | Find a user by their email address. Requires ADMIN or MANAGER role. |
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 10 tools
Authentication tools are clearly distinct, but personas and usuarios overlap conceptually. While descriptions distinguish 'people' from 'users', the boundary is unclear, and get_usuario_by_email could be confused with get_persona. There is potential for an agent to misselect between persona and usuario tools.
Most tools follow a consistent verb_noun pattern (list_personas, create_persona, delete_persona). Exceptions are login, logout, and get_me, which are imperative or pronoun-based but still readable. The overall naming is predictable and mostly consistent.
10 tools is well within the typical 3-15 range and appropriate for a management server covering authentication and entity CRUD. Each tool appears purposeful and the set is not bloated.
Persona CRUD is fully covered, and authentication has login, logout, and session info. However, usuario operations are limited to listing and fetching by email, lacking create, update, and delete. This creates an asymmetry and potential dead end if user management is expected in a 'Gestion' server.