charliehr_get_team_member_working_location — CharlieHR MCP by usefulapi MCP Tool
charliehr_get_team_member_working_location
(charliehr get team member working location) is one of 27 tools on the
CharlieHR MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call charliehr_get_team_member_working_location from your client
- Claude Code CharlieHR MCP by usefulapi charliehr_get_team_member_working_location run in your project directory
- Claude Desktop CharlieHR MCP by usefulapi charliehr_get_team_member_working_location ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CharlieHR MCP by usefulapi charliehr_get_team_member_working_location ~/.cursor/mcp.json
- VS Code CharlieHR MCP by usefulapi charliehr_get_team_member_working_location .vscode/mcp.json
- Zed CharlieHR MCP by usefulapi charliehr_get_team_member_working_location ~/.config/zed/settings.json
- Windsurf CharlieHR MCP by usefulapi charliehr_get_team_member_working_location ~/.codeium/windsurf/mcp_config.json
- Cline CharlieHR MCP by usefulapi charliehr_get_team_member_working_location ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CharlieHR MCP by usefulapi charliehr_get_team_member_working_location ~/.gemini/settings.json
- Grok CharlieHR MCP by usefulapi charliehr_get_team_member_working_location .mcp.json (in your project root)
- ChatGPT CharlieHR MCP by usefulapi charliehr_get_team_member_working_location Settings → Connectors → Advanced → Developer mode
- Claude.ai CharlieHR MCP by usefulapi charliehr_get_team_member_working_location Settings → Connectors → Add custom connector
- LangChain CharlieHR MCP by usefulapi charliehr_get_team_member_working_location pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http charliehr https://charliehr.usefulapi.io/mcpOther tools on this server
- charliehr_get_company
- charliehr_list_offices
- charliehr_get_office
- charliehr_list_teams
- charliehr_get_team
- charliehr_list_team_members
- charliehr_get_team_member
- charliehr_get_team_member_working_weeks
- charliehr_list_working_locations
- charliehr_list_leave_requests
- charliehr_get_leave_request
- charliehr_list_team_member_leave_requests
- charliehr_list_leave_allowances
- charliehr_get_team_member_leave_allowance
- charliehr_list_allowance_adjustments
- charliehr_list_non_holiday_leave_allowances
- charliehr_list_leave_types
- charliehr_get_leave_type
- charliehr_list_company_holidays
- charliehr_list_restricted_dates
- charliehr_list_salaries
- charliehr_list_team_member_salaries
- charliehr_list_team_member_note_types
- charliehr_get_team_member_note_type
- charliehr_list_team_member_notes
- charliehr_create_team_member_note
This list was read from the server itself, by connecting to it and calling tools/list on 23 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.