Read staff, rosters, timesheets and leave, and add or update staff in Microkeeper. For managers who roster staff and check timesheets in Microkeeper. 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": {
"microkeeper": {
"url": "https://microkeeper.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"microkeeper": {
"type": "http",
"url": "https://microkeeper.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 locations, then read the rostered shifts of every employee at the active locations, for up to 31 days.
microkeeper_get_locations microkeeper_get_roster
Read the timesheets for up to 31 days, for all staff or for the usernames you choose. Read staff profiles to match names.
microkeeper_get_timesheet microkeeper_get_employees
Read the leave requests that start, end or run through a date range, with their type and status.
microkeeper_get_leave
Add an employee, or update the fields you send for an existing one. Only the fields you send change. A login email is sent only when you set welcome.
Changes data · microkeeper_upsert_employees
List the jobs by status, and the groups of staff, such as teams and sites.
microkeeper_get_jobs microkeeper_get_group_config
The login page asks for your Microkeeper business key.
In Microkeeper, go to Menu → Settings → General → Global → Developers, then Manage Business API Keys. Keys are shown once. Your key is used only to call the API for your account.
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 Microkeeper business 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 Microkeeper connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
microkeeper_get_employees | read | Get employees Read staff profiles. Give changed_since (yyyy-mm-dd, up to a year back) for everyone changed since then, or ids with id_type for specific staff. With neither, returns all active staff. Action get_employees (HR/Staff, Read Only). |
microkeeper_get_group_config | read | Get groups Read the account's Groups (teams and sites that staff belong to). Action get_group_config (HR/Staff, Read Only). |
microkeeper_get_locations | read | Get locations Read every Location (site) with its LID, third_ID, address, active flag and managers. Action get_locations (Account, Read Only). |
microkeeper_get_roles | read | Get roles Read every Role (active and inactive) with its ROID and required skills. Action get_roles (Account, Read Only). |
microkeeper_get_jobs | read | Get jobs Read Jobs (projects, sites or functions staff clock to). Give JID or JobID lists for specific Jobs; otherwise status all or finished. Action get_jobs (Account, Read Only). |
microkeeper_get_roster | read | Get roster Read rostered shifts for every employee at active Locations, for up to 31 days (inclusive). Action get_roster (Roster, Read Only). |
microkeeper_get_timesheet | read | Get timesheets Read worked shifts for up to 31 days (inclusive), for all staff or the usernames given. Action get_timesheet (Roster, Read Only). |
microkeeper_get_leave | read | Get leave requests Read leave requests that start, end or run through a date range: type, dates and status. Action get_leave (Payroll, Read Only). |
microkeeper_upsert_employees | write | Add or update employees Add new staff or update existing ones (matched by EmployeeID, then eusername, then EID). Only the fields you send change. A new employee gets a login email only if you set welcome. Action upsert_employees (HR/Staff, Read/Write). |
microkeeper_upsert_locations | write | Add or update locations Add Locations or update them (matched by LID, or by third_ID). Locations you do not send stay as they are. Action upsert_locations (Account, Read/Write). |
microkeeper_update_jobs | write | Add or update jobs Add Jobs or update them (matched by JobID, or by JID; JID 0 adds). Jobs you do not send are not changed. Action update_jobs (Account, Read/Write). |
microkeeper_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. | |
microkeeper_request_feature | Request a missing feature Tell usefulapi that the user needs something the Microkeeper 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. | |
microkeeper_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Microkeeper (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. | |
microkeeper_cancel_subscription | Cancel the Pro subscription Cancel the caller's Microkeeper 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 microkeeper_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 Microkeeper server only. Subscribe with microkeeper_upgrade (it returns a Stripe Checkout link). Cancel any time with microkeeper_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running microkeeper_upgrade before then undoes the cancel. Or write to [email protected].
See who is rostered at a site. Check worked hours for a period. Find staff on leave. Add a new employee or update staff details. Review jobs and groups. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Microkeeper. The server calls the Microkeeper API with your own Microkeeper 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 Microkeeper business 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 Microkeeper business 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 Microkeeper 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 Microkeeper.
Yes, if you approve it. 3 of the 11 Microkeeper tools can create or change data. The other 8 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 Microkeeper server only. Cancel any time: Pro then runs to the end of the paid period. Run microkeeper_usage_status to see how many calls you used.
Ask the AI to run microkeeper_upgrade: it returns a Stripe Checkout link. To cancel, run microkeeper_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 microkeeper_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.