CharlieHR MCP by usefulapi
Server Details
Read CharlieHR team members, leave, allowances, offices, teams and salaries; add team member notes.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 27 tools
Most tools have clearly distinct resource+scope targets, and the systematic list (all/company) vs get/list_team_member (single member) split for leave requests, allowances and salaries keeps the plural/singular pairs separable. The one soft spot is charliehr_list_working_locations, which with a date silently becomes a per-member lookup overlapping charliehr_get_team_member_working_location, and list_team_member_notes vs list_team_member_note_types requires reading descriptions carefully. Overall an agent can reliably pick tools.
Every tool uses the same charliehr_ prefix plus a verb_noun pattern (get_, list_, create_) with snake_case throughout, e.g. charliehr_list_leave_types, charliehr_get_team_member_note_type. Scope modifiers (team_member, company) are applied predictably, so names are parseable and consistent across all 27 tools.
27 tools is at the heavy end, but the HR domain genuinely spans many resources (team members, teams, offices, leave types/requests, allowances, salaries, notes, working locations), and nearly every tool maps to a distinct endpoint rather than being a redundant wrapper. The large list/get pairing inflates the count somewhat, but each tool still earns its place.
Read coverage is strong and thorough across the HR domain, but the surface is almost entirely read-only: the sole write operation is charliehr_create_team_member_note. An agent cannot create or update a team member, approve/decline or submit a leave request, or delete a note, which are the obvious lifecycle operations an HR agent would expect, leaving notable gaps even if the upstream API is largely read-only.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read employees, leave, recruiting and reports; book or decide leave and add applicant notes.
Read people, employments, org units, absences and timesheets in Cezanne HR.
Read ChurchSuite contacts, children, small groups, rotas, events and attendance; add contact notes.
Read employees, clock-ins and absences; set employee external references in BrightHR.
1
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with the Officient HR API to manage people, days off, and salary slips through natural language.9MIT
- AlicenseBqualityDmaintenanceRead-only MCP server for the Humaans HRIS API, providing tools to query people, reporting chains, compensation, time away, and more.33MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural-language interaction with the full Planday API, including all 125 operations, composed timesheet reporting, staff cost summaries, and safe write access controls.MIT

HR Partner MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to read and write HR Partner company data via the HR Partner API, including employees, leave, expenses, recruitment, and more.49MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.