Read employees, attendance, leave and payroll; create employee records and import device punches. For HR and payroll teams with authorized Jisr Open 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": {
"jisr": {
"url": "https://jisr.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"jisr": {
"type": "http",
"url": "https://jisr.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.
Find employees by status or joining dates, then read an authorized employee profile. Profiles can include sensitive identity and contact information.
jisr_list_employees jisr_get_employee
Review attendance summaries and annual leave balances for a selected period or group of employees.
jisr_list_attendance_summary jisr_get_annual_leave_balances
Read payroll transactions for a confirmed pay period using a key with the required financial permissions. This does not send salary payments.
jisr_list_paygroups jisr_list_payroll_transactions
Create an employee record using lookup IDs. Jisr sends the employee an invitation email.
Changes data · jisr_list_lookup jisr_create_employee
Submit genuine device punches for asynchronous processing, then inspect the attendance logs. Submission does not guarantee every punch was accepted.
Changes data · jisr_create_attendance_punches jisr_list_attendance_punches
The login page asks for your Hosting region, Organization slug, Open API key and Open API secret.
In Jisr an administrator opens the Open API settings, creates a key, picks which APIs it may call (grant only what you need: payroll and financial data are separate permissions) and copies the key and secret (the secret is shown only once). The slug is the first part of your Jisr address (abcd for abcd.jisr.net). Choose Saudi cloud if your Jisr address ends in .jisr.net.sa. Use scoped credentials you authorize for this connection. Requested HR, attendance, payroll, bank/IBAN and identity records pass to your chosen AI client and its LLM provider; API credentials are not sent to the LLM. Choose only data you are authorized to process in that AI service. Tools can register employees (sending invitations) and submit device attendance punches, which may affect payroll. No salary payment or journal posting tools are exposed. Employee monthly payables requires vendor enablement. Revoke the API key in Jisr to stop access; already minted vendor sessions may remain valid until expiry.
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 Hosting region, Organization slug, Open API key and Open API 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 Jisr connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
jisr_list_employees | read | List employees List the organization's employees (active by default) with code, names (English/Arabic), job title, department, business unit, employment type, line manager, joining date and status. Filter by active/inactive status, creation date and joining, termination or deletion date ranges. If the API key also has the 'Get Employee Financial Info' / 'Accounting Info' permissions, Jisr adds salary, bank (IBAN) and accounting fields: sensitive HR data. GET /openapi/v1/employees. |
jisr_get_employee | read | Get employee One employee's profile by id (UUID from jisr_list_employees): names, code, gender, marital status, phone, emails, date of birth, passport/ID number, address, line manager, department, business unit, employment type, location, nationality and contract. GET /openapi/v1/employees/basic_info?id=. |
jisr_get_employee_financial_info | read | Get employee financial info One employee's financial details by id: salary components and bank account (IBAN). Sensitive payroll data; needs the 'Get Employee Financial Info' permission on the API key. GET /openapi/v1/employees/financial_info?id=. |
jisr_list_lookup | read | List lookup values List one of the organization's lookup tables: departments, employment_types, business_units, locations, nationalities or outsourcing_companies, with their ids and English/Arabic names. Use the ids when creating an employee. GET /openapi/v1/lookups/{table}. |
jisr_list_attendance_summary | read | List attendance summary Attendance summary per employee for a date range (default: the current month): total working hours, late arrival, early departure, extra and approved overtime, absence days and records. Filter by one employee or by active/inactive status. GET /openapi/v1/attendance/summary. |
jisr_list_attendance_punches | read | List attendance punches List raw clock-in/out punches that were received from punch devices, either the ones that were processed successfully or the ones that failed, in a time window (Jisr's default: the last hour). Each punch has id, punch_time, employee_code, terminal_sn and clocking_id. GET /openapi/v1/attendance_logs. |
jisr_get_annual_leave_balances | read | Get annual leave balances Annual leave balance summaries per employee (all employees, or only the given employee codes, at most 100). Only the annual leave type is supported by Jisr. GET /openapi/v1/employee_leaves/summary. |
jisr_list_paygroups | read | List pay groups List the organization's pay groups (id and name). The pay group id is needed for payroll and accrual queries. GET /openapi/v1/paygroups. |
jisr_list_payroll_transactions | read | List payroll transactions Payroll transactions per employee for one settlement type. type 'payrun' (the regular payroll) needs pay_period and paygroup_id; 'final_settlements', 'vacations_settlements' and 'out_off_payroll_transactions' need a from/to date range. Optionally filter by employee ids or transaction type ids (jisr_list_gl_transaction_types). Sensitive payroll data. GET /openapi/v1/payroll_transactions. |
jisr_list_accrual_transactions | read | List accrual transactions Accruals per employee for a confirmed pay period: vacations, end_of_service or tickets_provision (amount, vacation days). Sensitive payroll data. GET /openapi/v1/accrual_transactions. |
jisr_get_employee_monthly_payables | read | Get employee monthly payables One employee's payables for a month: net salary, earnings, additions and deductions with breakdowns. Only available to organizations Jisr has whitelisted for this API. Sensitive payroll data. GET /openapi/v1/employee_monthly_payables. |
jisr_list_gl_transaction_types | read | List transaction types List the payroll (GL) transaction types: id, category (allowances, loan types...), English/Arabic name and status. Use the ids to filter jisr_list_payroll_transactions. GET /openapi/v1/gl_transaction_types. |
jisr_list_audit_events | read | List audit events The organization's audit trail: who did what and when (module, feature, action, actor, success). Filter by module, event name, event type and a time range. GET /openapi/v1/audit_events. |
jisr_list_webhooks | read | List webhooks List the webhooks registered for the organization: name, endpoint host, method, status. Authentication data, custom header values and the endpoint's path and query (they can hold secrets) are hidden. Read-only; this server does not create or change webhooks. GET /openapi/v1/webhooks. |
jisr_create_employee | write | Create employee WRITE: register a new employee in Jisr (they are invited to the system by email). Not reversible through this server: there is no delete tool. Get department_id, employment_type_id, location_id and nationality_id from jisr_list_lookup first. Names need at least two parts. POST /openapi/v1/employees. |
jisr_create_attendance_punches | write | Import attendance punches WRITE: send a batch of raw clock-in/out punches (at most 100) from a punch device into Jisr attendance. Jisr processes them asynchronously; check the result with jisr_list_attendance_punches. Each punch carries the unique id its device generated; do not invent ids. POST /openapi/v1/attendance_logs. |
jisr_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. | |
jisr_request_feature | Request a missing feature Tell usefulapi that the user needs something the Jisr 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. | |
jisr_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Jisr (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. | |
jisr_cancel_subscription | Cancel the Pro subscription Cancel the caller's Jisr 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 jisr_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 Jisr 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 Jisr server only. Subscribe with jisr_upgrade (it returns a Stripe Checkout link). Cancel any time with jisr_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running jisr_upgrade before then undoes the cancel. Or write to [email protected].
Review employee records. Check attendance and leave. Review payroll transactions. Register a new employee. Import device attendance punches. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Jisr. The server calls the Jisr API with your own Jisr 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 Hosting region, Organization slug, Open API key and Open API 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 Hosting region, Organization slug, Open API key and Open API 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 Jisr 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 Jisr.
Yes, if you approve it. 2 of the 16 Jisr tools can create or change data. The other 14 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 Jisr server only. Cancel any time: Pro then runs to the end of the paid period. Run jisr_usage_status to see how many calls you used.
Ask the AI to run jisr_upgrade: it returns a Stripe Checkout link. To cancel, run jisr_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 jisr_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.