Read workflows, forms and brands; launch, update and cancel workflows in Enboarder. For HR teams that run onboarding and employee journeys with Enboarder. 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": {
"enboarder": {
"url": "https://enboarder.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"enboarder": {
"type": "http",
"url": "https://enboarder.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.
List the workflows and read the properties of one. Check the fields that a launch needs.
enboarder_list_workflows enboarder_get_workflow_properties
Read the data of launched workflows, or list the launched instances of one workflow by its id.
enboarder_get_workflow_data enboarder_get_workflow_data_by_id
List the forms and read the submissions of one form.
enboarder_list_forms enboarder_get_form_properties enboarder_get_form_data
Launch a workflow for a new employee with the person data.
Changes data · enboarder_get_workflow_properties enboarder_launch_workflow
Update the data of a running workflow, or cancel it if the hire does not start.
Changes data · enboarder_update_workflow enboarder_cancel_workflow
The login page asks for your Data region and Enboarder API key.
Find the key in Enboarder → Settings → Integration → Extensions. An admin must switch the REST API on there. Your key is used only to call the API on your behalf and to derive a private account id; 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 Data region and Enboarder API 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 Enboarder connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
enboarder_list_workflows | read | List workflows List workflow definitions (id, name, isActive). Start here to find workflow ids. GET /reports/workflows. |
enboarder_get_workflow_properties | read | Get workflow properties List the categories, custom fields and stakeholders (managers) configured for one workflow. GET /reports/workflows/{id}/properties. |
enboarder_get_workflow_data | read | Get workflow data List launched workflow instances (employee, status, start date, custom fields, managers) across all workflows. By default the last year. Returns up to one page; pass next_key for more. GET /reports/workflows/data. |
enboarder_get_workflow_data_by_id | read | Get data for one workflow List launched instances of ONE workflow (employee, status, start date, custom fields, managers). By default the last year. GET /reports/workflows/{id}/data. |
enboarder_list_forms | read | List forms List forms (id, name). GET /reports/forms. |
enboarder_get_form_properties | read | Get form properties List the questions (field names, types, options) of one form. GET /reports/forms/{id}/properties. |
enboarder_get_form_data | read | Get form submissions Get form submissions with questions, answers and the workflow custom fields. 500 records per page; pass next_key for more. GET /reports/forms/{id}/data. |
enboarder_get_profile | read | Get profile Get one employee profile by its external id (contact details, profile fields, optionally active workflows). GET /restapi/v1/profile/{id}. |
enboarder_list_brands | read | List brands List brands of the account. GET /restapi/v1/settings/brand/all. |
enboarder_list_locations | read | List locations List locations of the account. GET /restapi/v1/settings/location/all. |
enboarder_list_categories | read | List categories List categories of the account. GET /restapi/v1/settings/category/all. |
enboarder_list_custom_fields | read | List custom fields List custom fields of the account. GET /restapi/v1/settings/customfield/all. |
enboarder_launch_workflow | write | Launch a workflow (basic) WRITE: start an onboarding workflow for one employee with one manager (this can send messages to the employee and manager). Needs the employee full name, one contact (email or mobile), the manager full name and contact, and the start date. mode 0 (default) does not launch if the external id already exists. POST /restapi/v1/startwf/basic. |
enboarder_update_workflow | write | Update a running workflow WRITE: change a running workflow found by its external id (partial update: send only what changes, for example start_date or custom fields). Fails if the workflow is complete or cancelled. PUT /restapi/v1/updatewf. |
enboarder_cancel_workflow | write | Cancel a workflow WRITE (cannot be undone): cancel a running workflow found by its external id. mode ALL (default) cancels every workflow with that external id. POST /restapi/v1/cancelwf. |
enboarder_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. | |
enboarder_request_feature | Request a missing feature Tell usefulapi that the user needs something the Enboarder 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. | |
enboarder_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Enboarder (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. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise 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. | |
enboarder_cancel_subscription | Cancel the Pro subscription Cancel the caller's Enboarder 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 enboarder_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 Enboarder server only. Subscribe with enboarder_upgrade (it returns a Stripe Checkout link). Cancel any time with enboarder_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running enboarder_upgrade before then undoes the cancel. Or write to [email protected].
See which workflows exist. Review the data of a workflow. Read form submissions. Start onboarding for a new hire. Correct or stop a running workflow. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Enboarder. The server calls the Enboarder API with your own Enboarder 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 Data region and Enboarder API 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 Data region and Enboarder API 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 Enboarder 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 Enboarder.
Yes, if you approve it. 3 of the 15 Enboarder tools can create or change data. The other 12 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 Enboarder server only. Cancel any time: Pro then runs to the end of the paid period. Run enboarder_usage_status to see how many calls you used.
Ask the AI to run enboarder_upgrade: it returns a Stripe Checkout link. To cancel, run enboarder_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 enboarder_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.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.