Read intelliHR people, jobs, leave, skills and training; create and update people records. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"intellihr": {
"url": "https://intellihr.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"intellihr": {
"type": "http",
"url": "https://intellihr.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your intelliHR tenant and intelliHR access key.
The tenant is the first part of your intelliHR address (acme for acme.intellihr.io). Create the key in intelliHR under Settings → Public API Access Keys. intelliHR keys have no scopes: a key acts as a full system administrator, so create one just for this connection and delete it in intelliHR when you stop using it. Your key is used only to call the intelliHR API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your intelliHR tenant and intelliHR access key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the intelliHR connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
intellihr_list_people | read | List people List the people (employees) in intelliHR as at today: name, employee number, email, phone, addresses, emergency contact, employment status, their jobs (summary) and custom fields. Filter by name (matches any part of the name), email, employee number, job id, recently updated, or who is on extended leave. Health information is never returned. GET /people. |
intellihr_get_person | read | Get person One person's full record by id: names, date of birth, gender, employee number, contact details, addresses, emergency contact, employment status, jobs, work rights, user account and custom fields. Health information is never returned. GET /people/{id}. |
intellihr_list_person_documents | read | List a person's documents The documents stored on a person's record (file name, type, size, upload status and a download link). Contents are not read. GET /people/{personId}/documents. |
intellihr_list_person_skills | read | List a person's skills The skills assigned to a person (with their level and review details as intelliHR returns them). The whole list comes back at once. GET /people/{personId}/skills. |
intellihr_list_person_tasks | read | List a person's tasks Tasks (forms, reviews, check-ins, onboarding steps) for a person, by tab: DUE (default), ABOUT_ME, ABOUT_OTHERS, DONE or IGNORED. GET /people/{personId}/tasks. |
intellihr_list_jobs | read | List jobs List jobs (roles people hold, past, current and future) as at today: person, position title, location, business unit and entity, supervisor, work type, FTE, remuneration schedule, start/end dates and status. Filter by person, job title, status (Current Job, Future Job, Ending Job, Past Job), work type, primary job, or upcoming/recent end dates. GET /jobs. |
intellihr_get_job | read | Get job One job by id with its person, position title, location, business unit, supervisor, pay grade, remuneration and dates. GET /jobs/{id}. |
intellihr_get_job_timeline | read | Get job timeline The upcoming changes and current information about a job (scheduled changes, end date). GET /jobs/{jobId}/timeline. |
intellihr_list_locations | read | List locations The organisation's locations (sites) with parent location, code, address, enabled flag and representatives. GET /locations. |
intellihr_list_business_units | read | List business units The organisation's business units (departments, teams). Filter by name or identifier. GET /business-units. |
intellihr_list_business_entities | read | List business entities The organisation's business entities (legal employers). GET /business-entities. |
intellihr_list_position_titles | read | List position titles The position titles (job names) defined in intelliHR. Filter by name. GET /position-titles. |
intellihr_list_pay_grades | read | List pay grades The pay grades and their rates, optionally as at a date. GET /pay-grades. |
intellihr_list_users | read | List users The user accounts that can sign in to intelliHR: username, enabled flag, permission groups and the linked person. GET /users. |
intellihr_list_custom_field_definitions | read | List custom field definitions The custom fields defined in intelliHR (what each field on a person, job or location means and its type). GET /custom-field-definitions. |
intellihr_list_reference_data | read | List reference data Look up one of intelliHR's reference lists: employment_conditions, work_classes, work_types, work_rights, recruitment_sources, extended_leave_types, job_change_reasons, skill_disciplines, training_types, training_providers, qualification_types, qualification_library_items, onboarding_templates, permission_groups or representative_types. Use it to find the ids and names other tools need. |
intellihr_list_skills | read | List skills The skills catalogue, optionally only business-critical skills or one discipline. GET /skills. |
intellihr_list_qualifications | read | List qualifications Qualification records held by people (licences, certificates) with status and dates. Filter by person, employee number or library item. GET /qualifications. |
intellihr_list_trainings | read | List trainings Training records completed or booked by people, with provider, type and dates. Filter by training name, provider, type, employee number or email. GET /trainings. |
intellihr_create_person | write | Create person WRITE: create a new person record in intelliHR (last name required). It creates the person only: no job, no user account and no welcome email is sent. A job is added separately in intelliHR. Check with list_people first to avoid duplicates. POST /people. |
intellihr_update_person | write | Update person WRITE: change fields on an existing person (only the fields you pass change): names, date of birth, gender, employee number, title and emergency contact. Contact details, addresses and jobs are not changed by this tool. PATCH /people/{id}. |
intellihr_create_extended_leave | write | Create extended leave WRITE: record extended leave (parental, long service, unpaid, etc.) on an existing job. It changes the person's employment record and can trigger intelliHR workflows. The leave is created with the end date you give as expected; finalise it in intelliHR when the person returns. Find leave types with list_reference_data kind extended_leave_types. POST /extended-leave. |
intellihr_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
intellihr_request_feature | Request a missing feature Tell usefulapi that the user needs something the intelliHR tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
intellihr_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on intelliHR (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. Returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
intellihr_cancel_subscription | Cancel the Pro subscription Cancel the caller's intelliHR Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run intellihr_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this intelliHR server only. Subscribe with intellihr_upgrade (it returns a Stripe Checkout link). Cancel any time with intellihr_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running intellihr_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by intelliHR. The server calls the intelliHR API with your own intelliHR access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your intelliHR tenant and intelliHR access key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your intelliHR tenant and intelliHR access key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the intelliHR API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in intelliHR.
Yes, if you approve it. 3 of the 22 intelliHR tools can create or change data. The other 19 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this intelliHR server only. Cancel any time: Pro then runs to the end of the paid period. Run intellihr_usage_status to see how many calls you used.
Ask the AI to run intellihr_upgrade: it returns a Stripe Checkout link. To cancel, run intellihr_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with intellihr_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.