List shifts and groups, and filter for open shifts in Inzetrooster. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Inzetrooster connector, then ask in plain words. The AI picks the tools.
For volunteer and staff coordinators who fill shifts in Inzetrooster.
List the shifts of the coming weeks and keep only the open ones. The open filter applies to the returned page only.
List the groups that have shifts in a date window, with the shift count of each. Counts come from the first 500 shifts only, so use a narrow window. Then list the shifts of one group.
List the shifts of one month, filtered by group, location or weekday, to see which shifts are covered.
List the shifts of one group in a week. The result includes the names of the assigned volunteers, for a reminder list.
The login page asks for your Inzetrooster account name and Inzetrooster API token.
Your account name is the part after inzetrooster.nl/ in your address. Ask Inzetrooster support for an API token (premium accounts only). Your token is used only to read your shifts on your behalf and to derive a private account id; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"inzetrooster": {
"url": "https://inzetrooster.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"inzetrooster": {
"type": "http",
"url": "https://inzetrooster.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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 Inzetrooster account name and Inzetrooster 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.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per user | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Inzetrooster server only. Ask your AI to run inzetrooster_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with inzetrooster_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with inzetrooster_upgrade before then undoes the cancel. Or write to [email protected].
inzetrooster_list_shiftsinzetrooster_list_groupsinzetrooster_usage_statusinzetrooster_request_featureinzetrooster_upgradeinzetrooster_cancel_subscriptionFind shifts that still need a person. Count the shifts of each group. Check the cover for one month. Prepare a reminder list for a group. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Inzetrooster. The server calls the Inzetrooster API with your own Inzetrooster 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 Inzetrooster account name and Inzetrooster API token. 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 Inzetrooster account name and Inzetrooster 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 Inzetrooster 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 Inzetrooster.
All 2 Inzetrooster tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Inzetrooster server only. Cancel any time: your paid plan then runs to the end of the paid period. Run inzetrooster_usage_status to see how many calls you used.
Ask the AI to run inzetrooster_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run inzetrooster_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with inzetrooster_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.