employee-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | Yes | MySQL host | |
| DB_NAME | Yes | MySQL database name | |
| DB_USER | Yes | MySQL user | |
| DB_PASSWORD | Yes | MySQL password |
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 |
|---|---|
| list_employeesA | Returns all employees |
| search_employeeB | Find employee by name |
| employees_by_departmentB | Returns employees from one department |
| add_employeeC | Adds a new employee |
| highest_salaryA | Returns highest paid employee |
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 5 tools
Each tool has a clear purpose: list all, search by name, filter by department, add, and find highest salary. While search and department filtering overlap with listing, the descriptions clarify specific query intents, so ambiguity is minimal.
Tool names follow mixed conventions: list_employees, search_employee, and add_employee use verb_noun, but employees_by_department and highest_salary do not follow that pattern. The names are still readable and descriptive, but not fully consistent.
With 5 tools, the server is well-scoped for employee management. Each tool covers a distinct need without excessive fragmentation or bloat, fitting comfortably in the ideal range.
Provides read and create operations (list, search, department filter, add, highest salary) but lacks update and delete operations. This is a notable gap for a full employee management lifecycle.