MCP Connector

The Skailer MCP server gives an AI assistant secure access to your HR data through OAuth authorization. Once connected, you can ask about employees, goals, and time off directly in a conversation - no API client required.

MCP (Model Context Protocol) is an open standard, so the server works with any client that supports it - Claude, other assistants, and your own integrations.

Connect

If your client has a connector directory, add Skailer from there. For Claude:

https://claude.ai/directory/connectors/skailer

For any other MCP client, connect manually using the server address:

https://mcp.skailer.com/mcp

On first use the client redirects you to Skailer for OAuth authorization. The server acts on behalf of the user who authorized it and respects that user’s permissions - it cannot read or change anything the user has no access to.

What the server can do

Session

• check_token - check that the access token is valid.
• get_me - return the profile of the currently authorized user.

Employees

• search_employees - search employees by name, position, department, and other fields.
• get_employee - get an employee card by id.
• get_employee_by_email - get an employee card by email.

Goals and OKR

• search_goals - search goals with filters.
• get_goal - get a goal with its key results.
• create_goal - create a goal.
• update_goal - update a goal.
• delete_goal - delete a goal.
• checkin_goal - post a check-in with current progress.
• create_key_result - add a key result to a goal.
• update_key_result - update a key result.
• delete_key_result - delete a key result.

Time off

• search_employee_time_off - search employee time-off requests.
• get_employee_time_off_balance - get an employee’s balance on a date.
• get_employee_time_off_calendar - get an employee’s time-off calendar.
• list_employee_time_off_categories - list the organization’s time-off categories.

Notes

• The server changes data: create_*, update_*, delete_*, and checkin_goal write to Skailer. Review what the assistant proposes before confirming such an action.
• Access is limited by the authorizing user’s permissions, so give the integration user only the rights it actually needs.
• The server uses the same Public API described in this documentation, so its behavior matches the corresponding endpoints.