Humaans MCP server

Read from the package source without running it. The installed server may list more.

• approve_humaans_time_away

  Approve a pending time away request in Humaans (manager action). Sets the request status to approved. Use list_humaans_time_away with requestStatus="pending" to find requests awaiting review. Example: { "timeAwayId": "YLlqHE4DLvGtFJ7L2qro6bTF" } RELATED TOOLS: - decline_humaans_time_away: Decline the request instead - list_humaans_time_away: Find pending requests

• cancel_humaans_time_awaywrite action

  Cancel a time away entry in Humaans (deletes it permanently). Use this to withdraw a time off request or remove an incorrect entry. The deletion cannot be undone — confirm the entry with list_humaans_time_away first. Example: { "timeAwayId": "YLlqHE4DLvGtFJ7L2qro6bTF" } RELATED TOOLS: - list_humaans_time_away: Find the timeAwayId to cancel - create_humaans_time_away: Create a new request instead

• configure_humaans_api_key

  Host-managed setup only. The user adds the Humaans API access token in Settings → Connectors in the app. Do not ask for or accept the token in chat.

• create_humaans_time_awaywrite action

  Create a time away request in Humaans (PTO, sick leave, etc.). WORKFLOW - To request time off: 1. Call get_humaans_me to get your personId 2. Call list_humaans_time_away_types to find the timeAwayTypeId (e.g., "Paid time off") 3. Call this tool with the details Dates must be in YYYY-MM-DD format. Use startPeriod/endPeriod for half days. COMMON MISTAKES: - Don't guess timeAwayTypeId - always get it

• decline_humaans_time_away

  Decline a pending time away request in Humaans (manager action). Sets the request status to declined. Consider including a reviewNote so the employee knows why. Example: { "timeAwayId": "YLlqHE4DLvGtFJ7L2qro6bTF", "reviewNote": "Dates clash with the release freeze" } RELATED TOOLS: - approve_humaans_time_away: Approve the request instead - list_humaans_time_away: Find pending requests

• get_humaans_company

  Get company information from Humaans. Returns: company name, status, trial info, timesheet settings. Example: {}

• get_humaans_job_role

  Get a specific job role by ID from Humaans. Returns: job title, department, manager (reportingTo), effectiveDate, endDate, note. Example: { "jobRoleId": "hmA5GnUq9ojK86LLKKWbiuKG" }

• get_humaans_me

  Get the current authenticated user's profile from Humaans. Returns: name, email, job title, department, teams, location, status. Use this to get your own personId for other operations (e.g., creating time away). RELATED TOOLS: - create_humaans_time_away: Use the returned id as personId - list_humaans_time_away: Filter by your personId

• get_humaans_person

  Get full employee profile from Humaans by their ID. Returns detailed profile including: name, email, job role, department, teams, location, employment dates, contract type, working days, manager, bio, social links. Sensitive fields (tax ID, personal email, home address) are redacted for privacy. Example: { "personId": "VMB1yzL5uL8VvNNCJc9rykJz" } WORKFLOW - To find a person: 1. Call list_humaans_p

• list_humaans_job_roles

  List job role history for employees in Humaans. Each person can have multiple job roles over time. The role with the most recent effectiveDate that is not in the future is the current active role. Use the asOf parameter to find what role someone had at a specific date. Example: { "personId": "VMB1yzL5uL8VvNNCJc9rykJz" } RELATED TOOLS: - list_humaans_people: Find personId to filter by

• list_humaans_locations

  List company locations/offices from Humaans. Returns: label, city, country, timezone for each office location. Note: Remote employees have locationId="remote" with remoteCity/remoteCountry fields on their person profile. Example: {}

• list_humaans_people

  List employees from Humaans HR. By default returns only active employees. Use status filter for other groups. Returns compact summaries: id, name, email, job title, department, teams, location, status. Example: { "status": "active", "team": "Engineering", "limit": 50 } Pagination: Returns up to 'limit' results (default 50, max 250). Use 'skip' for next page. RELATED TOOLS: - get_humaans_person: Pa

• list_humaans_teams

  List team names in Humaans with member counts. Humaans has no dedicated teams endpoint, so this derives the team list by scanning the people directory. Use it to discover valid values for the 'team' filter on list_humaans_people. Example: {} RELATED TOOLS: - list_humaans_people: Filter employees by team name

• list_humaans_time_away

  List time away (PTO, sick leave, etc.) entries from Humaans. Filter by person, date range, or approval status. Returns: dates, type, days count, approval status, notes. Example: { "personId": "VMB1yzL5uL8VvNNCJc9rykJz" } Example: { "startDateAfter": "2024-01-01", "startDateBefore": "2024-12-31" } RELATED TOOLS: - list_humaans_people: Find personId to filter by - list_humaans_time_away_types: See a

• list_humaans_time_away_allocations

  List time away allocations in Humaans — which time off policy applies to each person, and from which date. Allocations link a person to a time away policy (the policy defines their allowance and balances). Use this to answer "which PTO policy is Jane on?" or "who is on the US policy?". Example: { "personId": "VMB1yzL5uL8VvNNCJc9rykJz" } RELATED TOOLS: - list_humaans_people: Find personId to filter

• list_humaans_time_away_types

  List available time away types in Humaans. Returns type names and IDs (e.g., "Paid time off", "Sick leave", "Working from home"). You need the type ID to create a time away request. RELATED TOOLS: - create_humaans_time_away: Use the returned id as timeAwayTypeId

• Code scan33 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

85/100

higher than 75% of 4,456 AI and agents servers

Tools

16

the typical AI and agents server has 7

Tools that change things

13%

typical: 3%. Fewer write tools means less an agent can break

GitHub stars

14

more than 86% of 2,733 AI and agents servers

Downloads a week

76

more than 51% of 1,712 AI and agents servers with a package

Humaans: common questions

Is Humaans MCP server safe?

Yes, by our scan: it is graded A (85/100). Read the Humaans safety report

How do I install Humaans?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Humaans need an API key?

Yes. The registry entry asks for HUMAANS_API_KEY.

Is Humaans maintained?

The last commit was 11 days ago (2026-11-04). The latest release is v0.3.1.

What can I use instead of Humaans?

Servers from other publishers that do the same job: DCC-MCP Core MCP server.

How does Humaans compare with other AI and agents MCP servers?

safety score 85/100 (higher than 75% of 4,456 AI and agents servers); tools 16 (the typical AI and agents server has 7); tools that change things 13% (typical: 3%. Fewer write tools means less an agent can break). Full comparison.