Read PaySpace employees, organization, payroll runs, payslips and leave records. Read-only. 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": {
"payspace": {
"url": "https://payspace.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"payspace": {
"type": "http",
"url": "https://payspace.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.
The login page asks for your Client ID and Client secret.
A company administrator creates them in PaySpace under Config > Basic Settings > General Company > Integrations > API Credentials (the secret is shown only once, copy it when you save). The values are used only to get short-lived access tokens and read from the PaySpace API on your behalf; they are never shown to anyone. Employee, payslip and leave records are personal data.
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 Client ID and Client secret. 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 PaySpace connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
payspace_list_companies | read | List companies List the companies (id, code, name, group) the API credentials can access. Company ids go into the company_id argument of the other tools. From the token reply of POST /connect/token. |
payspace_list_employees | read | List employees List active employees of a company with their biographical details (name, employee number, contact, dates). Personal data. GET /odata/v2.0/{company}/Employee. Use payspace_list_all_employees to include terminated employees. |
payspace_list_all_employees | read | List all employees (incl. terminated) List all employees of a company including terminated ones. Personal data. GET /odata/v2.0/{company}/Employee/all. |
payspace_get_employee | read | Get an employee Get one employee's biographical record by EmployeeId (the numeric id from payspace_list_employees). Personal data. GET /odata/v2.0/{company}/Employee({id}). |
payspace_list_employee_positions | read | List employee positions List employee position records (job, organization unit, grade, manager, effective dates). GET /odata/v2.0/{company}/EmployeePosition. |
payspace_list_employment_statuses | read | List employment statuses List employee employment status records (hire, termination, reason, dates). GET /odata/v2.0/{company}/EmployeeEmploymentStatus. |
payspace_list_suspensions | read | List employee suspensions List employee suspension records. GET /odata/v2.0/{company}/EmployeeSuspension. |
payspace_list_organization_units | read | List organization units List the organization hierarchy units (departments, divisions, cost centres) of a company. GET /odata/v2.0/{company}/OrganizationUnit. |
payspace_list_organization_positions | read | List organization positions List the organization positions (position details) defined for a company. GET /odata/v2.0/{company}/OrganizationPositionDetail. |
payspace_list_jobs | read | List jobs List the jobs defined in job management for a company. GET /odata/v2.0/{company}/JobManagement. |
payspace_list_regions | read | List regions List the company's regions. GET /odata/v2.0/{company}/CompanyRegion. |
payspace_list_payroll_frequencies | read | List payroll frequencies List the payroll frequencies of a company (the CompanyFrequency lookup). A value goes into the frequency argument of payspace_list_payroll_components, payspace_list_payroll_runs and payspace_list_recurring_components. GET /odata/v2.0/{company}/Lookup/CompanyFrequency. |
payspace_list_payroll_runs | read | List payroll runs List the payroll runs (periods) of a company for one frequency (the CompanyRun lookup). A value goes into the period argument of payspace_list_payroll_components and payspace_list_recurring_components. GET /odata/v2.0/{company}/Lookup/CompanyRun?frequency=. |
payspace_list_payroll_components | read | List payroll components List the company's payroll components (earnings, deductions, contributions) with their codes, for one payroll frequency and run. Get frequency from payspace_list_payroll_frequencies and period from payspace_list_payroll_runs. GET /odata/v2.0/{company}/ComponentCompany?frequency=&period=. |
payspace_list_recurring_components | read | List an employee's recurring components or loans List the recurring payroll components (EmployeeComponent) or loans (EmployeeLoan) of ONE employee for a payroll frequency and run. Personal data (pay). Get frequency from payspace_list_payroll_frequencies and period from payspace_list_payroll_runs. GET /odata/v2.0/{company}/{entity}?frequency=&period=&$filter=EmployeeNumber eq '...'. |
payspace_list_payslips | read | List payslips for a month List employee payslips (totals per employee) for a calendar year and month. Personal data (pay). GET /odata/v2.0/{company}/EmployeePayslip/{year}/{month}. |
payspace_list_payslip_lines | read | List payslip lines for a month List the payslip lines (one per component per employee: code, description, amount) for a calendar year and month. Personal data (pay). GET /odata/v2.0/{company}/EmployeePayslipLine/{year}/{month}. |
payspace_list_leave_applications | read | List leave applications List employee leave applications (type, dates, days, status). Give year and month together to restrict to a period. Personal data (absence). GET /odata/v2.0/{company}/EmployeeLeaveApplication[/{year}/{month}]. |
payspace_list_leave_adjustments | read | List leave adjustments List employee leave adjustments (manual changes to leave balances). Personal data. GET /odata/v2.0/{company}/EmployeeLeaveAdjustment. |
payspace_list_leave_entitlements | read | List leave entitlements List employee leave setup entitlements (leave type, days per cycle). GET /odata/v2.0/{company}/EmployeeLeaveSetupEntitlement. |
payspace_list_records | read | List records of another entity List records of another read-only entity set: CompanyEmploymentCategory, CompanyEmploymentSubCategory, CompanyLeaveReason, CompanyPositionFamily, CompanyPositionFunctionArea, CompanyTrainingCourse, CompanyQualification, CostingProjectActivity, OrganizationGrade, EmployeeAsset, EmployeeClaim, EmployeeDependant, EmployeeIncident, EmployeePayRate, EmployeeProject, EmployeeQualification, EmployeeSkill, EmployeeOutOfOffice. GET /odata/v2.0/{company}/{entity}. Employee-level entities contain personal data. |
payspace_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. | |
payspace_request_feature | Request a missing feature Tell usefulapi that the user needs something the PaySpace 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. | |
payspace_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on PaySpace (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. | |
payspace_cancel_subscription | Cancel the Pro subscription Cancel the caller's PaySpace 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 payspace_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 company | $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 PaySpace server only. Subscribe with payspace_upgrade (it returns a Stripe Checkout link). Cancel any time with payspace_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running payspace_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by PaySpace. The server calls the PaySpace API with your own PaySpace 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 Client ID and Client secret. 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 Client ID and Client secret. 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 PaySpace 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 PaySpace.
All 21 PaySpace tools are marked read-only.
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 PaySpace server only. Cancel any time: Pro then runs to the end of the paid period. Run payspace_usage_status to see how many calls you used.
Ask the AI to run payspace_upgrade: it returns a Stripe Checkout link. To cancel, run payspace_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 payspace_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.