Skip to main content
Glama

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

A3.5/5.0

Scored across 27 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness3/5

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

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.