MCP server for Arcoro and ExakTime — workforce data, jobs, cost codes and locations. For workforce and HR teams with enabled Arcoro or ExakTime API access. 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": {
"exaktime": {
"url": "https://exaktime.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"exaktime": {
"type": "http",
"url": "https://exaktime.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.
Read time records, punches and shifts to investigate a selected period.
exaktime_list_time_records exaktime_list_time_punches exaktime_list_shifts
List employees and departments, then inspect a selected employee within the API key permissions.
exaktime_list_employees exaktime_get_employee exaktime_list_departments
Read time-off requests and balances alongside the relevant pay periods.
exaktime_list_time_off_requests exaktime_list_time_off_balances exaktime_list_pay_periods
Review jobs and cost codes, then create a job or update a cost code when requested. These tools change reference records.
Changes data · exaktime_list_jobs exaktime_list_cost_codes exaktime_create_job exaktime_update_cost_code
The login page asks for your Arcoro API key.
Create it in the Arcoro API Portal (my.arcoro.com/api/portal; ask Arcoro support for access if you do not see it). A read-only key is enough for reports; a read-write key also lets the assistant create and update jobs, cost codes and locations. Use a dedicated key with only the permissions and licensed modules you need. Requested workforce, time, HR and OData benefits data passes to your chosen AI client and its LLM provider; it can include birth dates and masked tax identifiers. The six write tools create or update jobs, cost codes and locations. Revoke the key in Arcoro to stop access. Billing follows the Arcoro tenant when OData identifies it; keys without OData access use a key-based identity that changes on rotation.
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 Arcoro 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 ExakTime / Arcoro connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
exaktime_list_employees | read | List employees List employees (Person records of type Employee) with name, job title, department, employee id, active/inactive status and which Arcoro modules they use. Use personId with exaktime_get_employee. GET /v1/Common/Persons/Employees. |
exaktime_list_persons | read | Search persons List or search Person records (employees and API users) by first name, last name, employee identifier or work email. Returns personId, names, work email, employee id, username and whether the person is a contractor or deleted. GET /v1/Common/Persons. |
exaktime_get_person | read | Get person One Person record: names, contact details, address, login username and security groups. Government identifiers are not available through this server. GET /v1/Common/Persons/{personId}. |
exaktime_get_employee | read | Get employee Employment details for a person: hire/termination date, status, employment and pay type, pay rates, job code, manager, location, department, pay schedule and union. GET /v1/Common/Persons/{personId}/Employees. |
exaktime_list_locations | read | List locations List locations (job sites and offices) with address, coordinates, active flag and whether they are used for time and attendance. GET /v1/Common/Locations. |
exaktime_get_location | read | Get location One location by id. GET /v1/Common/Locations/{id}. |
exaktime_list_jobs | read | List jobs List jobs (projects) with identifier, name, active flag, dates, department, parent job and assigned locations. GET /v1/Time/Jobs. |
exaktime_get_job | read | Get job One job by id. GET /v1/Time/Jobs/{id}. |
exaktime_list_cost_codes | read | List cost codes List cost codes (phases and work activities that time is booked against) with identifier, name, active flag and cost type. GET /v1/Time/CostCodes. |
exaktime_get_cost_code | read | Get cost code One cost code by id. GET /v1/Time/CostCodes/{id}. |
exaktime_list_cost_types | read | List cost types List cost types (groupings of cost codes, e.g. labor, equipment) with identifier, name and active flag. GET /v1/Time/CostTypes. |
exaktime_list_departments | read | List departments List departments with identifier, name and active flag. GET /v1/Common/Departments. |
exaktime_list_job_codes | read | List job codes List job codes (positions / trades) with name, description and active flag. GET /v1/Common/JobCodes. |
exaktime_list_pay_schedules | read | List pay schedules List pay schedules with frequency, first pay date, pay periods per year and the default flag. GET /v1/Payroll/PaySchedules. |
exaktime_list_labor_classes | read | List labor classes List labor classes with identifier, name and active flag. GET /v1/Payroll/LaborClasses. |
exaktime_list_rate_codes | read | List rate codes List payroll rate codes with identifier, name, description and whether it is the base rate. GET /v1/Payroll/RateCodes. |
exaktime_list_time_records | read | List time records List time records (timecard entries: who worked, when, on which cost code and location, regular/overtime hours). Filter by work date range, person, location or cost code identifier; newest first. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwTimeRecords. |
exaktime_list_time_punches | read | List time punches List raw clock punches (punch time, device type, location, network time difference). Filter by date range (UTC days), person or location; newest first. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwTimePunches. |
exaktime_list_shifts | read | List scheduled shifts List scheduled shifts (employee, start/end, title, cost code, location, notes). Filter by start date range (UTC days), person or location; newest first. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwShifts. |
exaktime_list_pay_periods | read | List pay periods List pay periods (id, start and end date, closed or open, type), newest first. Use the id to find approvals. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwPayPeriods. |
exaktime_list_time_off_requests | read | List time off requests List time off requests (employee, plan, start/end date, hours, status, comments, manager). Filter by status, person or start-date range. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwTimeOffRequests. |
exaktime_list_time_off_balances | read | List time off balances List time off balances per employee and plan (balance hours, maximum balance, manager). Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwTimeOffBalances. |
exaktime_list_timecard_approvals | read | List daily timecard approvals List daily timecard approvals (work date, approval type, who approved and when, the employee). Filter by work date range or employee. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwWorkDateTimeApprovals. |
exaktime_list_pay_period_approvals | read | List pay period approvals List pay period (timesheet) approvals and sign-offs: pay period, approval type, approver, time, employee, comment. Use it to see who has not yet signed off. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwPayPeriodApprovals. |
exaktime_list_meal_break_violations | read | List meal break violations List meal break compliance violations (type, date, expected vs actual value) linked to a time record id. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/DwMealBreakViolations. |
exaktime_query_odata | read | Query any OData entity set Read-only OData query over any Arcoro data warehouse entity set, for questions the other tools do not cover (equipment, expenses, users, time records by hour group, learning, performance, recruiting, benefits...). Entity sets start with Dw, e.g. DwUsers, DwEquipments, DwExpenses, DwCostCodes, DwLocations, DwTimeRecordByHourGroups, DwEmploymentStatusHistories. Full list: https://my.arcoro.com/api/odata ; schema: https://api.arcoro.com/odata/$metadata. $filter uses OData v4 syntax, e.g. startswith(LastName,'Sm') and IsActive eq true. Source: the read-only OData data warehouse, refreshed nightly, so today's entries may not show until tomorrow. Page with skip/next_skip. GET /odata/{EntitySet}. |
exaktime_create_job | write | Create job WRITE: create a job (project) that employees can book time to. Identifier must be unique. The job appears in Arcoro right away; it can be deactivated again with exaktime_update_job (there is no delete). POST /v1/Time/Jobs. |
exaktime_update_job | write | Update job WRITE: change fields of an existing job (rename it, set dates, assign locations, or set is_active=false to close it). Only the fields you pass change (null clears a nullable field); the tool reads the job first and sends the full object, because Arcoro replaces the job on PUT. Two edits to the same job at the same moment can overwrite each other: run them one after the other. PUT /v1/Time/Jobs/{id}. |
exaktime_create_cost_code | write | Create cost code WRITE: create a cost code (phase or work activity) that time can be booked against. The name must be unique. It can be deactivated again with exaktime_update_cost_code (there is no delete). POST /v1/Time/CostCodes. |
exaktime_update_cost_code | write | Update cost code WRITE: change fields of an existing cost code (rename it, change its cost type, or set is_active=false to retire it). Only the fields you pass change; the tool reads the cost code first and sends the full object. PUT /v1/Time/CostCodes/{id}. |
exaktime_create_location | write | Create location WRITE: create a location (job site or office). Add the address and/or latitude and longitude so geofencing and maps work. It can be deactivated again with exaktime_update_location (there is no delete). POST /v1/Common/Locations. |
exaktime_update_location | write | Update location WRITE: change fields of an existing location (rename, move, new address, or set is_active=false to retire it). Only the fields you pass change; the tool reads the location first and sends the full object. PUT /v1/Common/Locations/{id}. |
exaktime_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. | |
exaktime_request_feature | Request a missing feature Tell usefulapi that the user needs something the ExakTime (Arcoro Time) 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. | |
exaktime_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on ExakTime (Arcoro Time) (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. | |
exaktime_cancel_subscription | Cancel the Pro subscription Cancel the caller's ExakTime (Arcoro Time) 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 exaktime_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 verified tenant (API key when tenant is unavailable) | $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 ExakTime / Arcoro server only. Subscribe with exaktime_upgrade (it returns a Stripe Checkout link). Cancel any time with exaktime_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running exaktime_upgrade before then undoes the cancel. Or write to [email protected].
Review recorded time. Find workforce details. Review time off. Maintain job and cost-code records. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by ExakTime / Arcoro. The server calls the ExakTime / Arcoro API with your own ExakTime / Arcoro 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 Arcoro API key. See Before you connect for where to find it.
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 Arcoro 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 ExakTime / Arcoro 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 ExakTime / Arcoro.
Yes, if you approve it. 6 of the 32 ExakTime / Arcoro tools can create or change data. The other 26 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 ExakTime / Arcoro server only. Cancel any time: Pro then runs to the end of the paid period. Run exaktime_usage_status to see how many calls you used.
Ask the AI to run exaktime_upgrade: it returns a Stripe Checkout link. To cancel, run exaktime_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 exaktime_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.