Read Workyard employees, projects, time cards and geofences; approve time cards and add notes. For contractors and operations teams tracking crews in Workyard. 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": {
"workyard": {
"url": "https://workyard.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"workyard": {
"type": "http",
"url": "https://workyard.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 working time cards and match employee IDs to crew names before checking current staffing.
workyard_list_time_cards workyard_list_employees
Find submitted time cards for a date range, inspect their details and read activity segments before a payroll review.
workyard_list_time_cards workyard_get_time_card workyard_list_time_card_activity_segments
Look up projects, find their geofences and check which projects are attached to a work site.
workyard_list_projects workyard_list_geofences workyard_list_geofence_projects
Approve one specific time card after reviewing its details. Approval feeds payroll and may not be reversible through the API.
Changes data · workyard_get_time_card workyard_approve_time_card
Add a note to a specific time card to record a correction explanation or a supervisor check. Each call creates a new note.
Changes data · workyard_add_time_card_note
The login page asks for your Workyard API token.
Optional: Organization ID.
In Workyard (web or desktop app) go to Integrations → API Token → Generate API Token (account Admin; API access needs the Autopilot plan). The Organization ID is only needed if your token sees several organizations. Your token is used only to call the Workyard 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 Workyard API token. 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 Workyard connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
workyard_get_organization | read | Get Workyard organization The organization this connection uses (id, name, settings such as timezone) from GET /orgs/{org_id}. |
workyard_list_employees | read | List Workyard employees List employees of the organization (employee_id, profile_id, name, title, role, status, contact data). Filter by status (active, removed, saas_disabled, expired; comma list), email, role name or free-text search. Paged: use next_page. |
workyard_list_projects | read | List Workyard projects List projects (id, name, identifier, customer, locations). Optionally filter by name or archived state. Paged: use next_page. |
workyard_get_project | read | Get Workyard project One project by id (workyard_list_projects gives the ids). |
workyard_list_time_cards | read | List Workyard time cards List time cards (id, employee_id, start_dt_unix, end_dt_unix, status, approver, totals). Workyard returns only status=working when no status is given, so pass status (for example submitted,approved) for finished work. Filter by employee and by start time (unix seconds, interpreted in the organization timezone). Paged: use next_page; the reply also carries time_summary. |
workyard_get_time_card | read | Get Workyard time card One time card by id, with its details (workyard_list_time_cards gives the ids). |
workyard_list_time_card_activity_segments | read | List Workyard time card activity segments The activity segments of one time card (where and on which project the employee worked, segment by segment). Not paged. |
workyard_list_geofences | read | List Workyard geofences (work sites) List geofences / work sites (id, name, place, enabled, radius). Filter by name, enabled state or project. Paged: use next_page. |
workyard_list_active_geofences | read | List active Workyard geofences All active geofences with limited data (Workyard: GET active_geofences). It does not say who is clocked in; use workyard_list_time_cards with status working for that. |
workyard_list_geofence_projects | read | List projects of a Workyard geofence The projects attached to one geofence (work site). Paged: use next_page. |
workyard_approve_time_card | write | Approve a Workyard time card WRITE: approve ONE time card (PATCH .../time_cards/{id}/approve). Approval feeds payroll in Workyard and may not be undoable through the API: only call it when the user asked to approve this exact time card. |
workyard_add_time_card_note | write | Add a note to a Workyard time card WRITE: add a text note to one time card (POST .../time_cards/{id}/notes). Adds a new note on every call; it does not edit or delete existing notes. |
workyard_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. | |
workyard_request_feature | Request a missing feature Tell usefulapi that the user needs something the Workyard 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. | |
workyard_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Workyard (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. | |
workyard_cancel_subscription | Cancel the Pro subscription Cancel the caller's Workyard 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 workyard_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 organization | $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 Workyard server only. Subscribe with workyard_upgrade (it returns a Stripe Checkout link). Cancel any time with workyard_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running workyard_upgrade before then undoes the cancel. Or write to [email protected].
Check who is clocked in. Review submitted time cards. Find projects and work sites. Approve a reviewed time card. Add context to a time card. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Workyard. The server calls the Workyard API with your own Workyard 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 Workyard API token. 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 Workyard API token. 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 Workyard 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 Workyard.
Yes, if you approve it. 2 of the 12 Workyard tools can create or change data. The other 10 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 Workyard server only. Cancel any time: Pro then runs to the end of the paid period. Run workyard_usage_status to see how many calls you used.
Ask the AI to run workyard_upgrade: it returns a Stripe Checkout link. To cancel, run workyard_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 workyard_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.