Schema | Gestion MCP Server

Gestion MCP Server

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

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ErnestoZeferinoDiaz/HumanResourcesManagement-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server