Connect Jisr to ChatGPT via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Jisr, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Jisr + ChatGPT

Ask about your Jisr HR organization from any AI assistant: employees and their job data, attendance summaries and punches, annual leave balances, departments and locations. Read-only by default; submitting attendance punches is available but switched off.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

JISR_SLUG, JISR_API_KEY, JISR_API_SECRET

Step 1 — Get credentials

Setting up takes about 5 minutes. You need a Jisr user with the Admin role, because only an Admin can create API keys, and your organization slug, the subdomain of your Jisr address.

1. In Jisr, open Settings → Webhook & API Keys → API Keys and click Add new API key (Jisr help article).
2. Name the key and tick the APIs it may use: Get List Employees, Get Employee Basic Information, Get attendance summary, View attendance records, View summary of employee annual leave, and the lookups you want. Tick Get Employee Financial Info only if the AI may see salaries.
3. Click Generate and copy the API key into JISR_API_KEY and the secret into JISR_API_SECRET. Jisr shows the secret only once: if it is lost, generate a new key.
4. Set JISR_SLUG to your organization slug: the subdomain of your Jisr address in lower case, acme for acme.jisr.net, not the full address.
5. Install the connector. Run jisr_list_employees to check the connection.

Cloud and self-hosted work the same way: there is no app to register and no redirect URL; the connector only needs the slug, the API key and the secret.

The connector signs in by itself: it calls POST /openapi/v1/auth with your slug, API key and secret, receives an access token and sends it as the Access-Token header, with slug and api-version, on every call. The key and the secret go only to that sign-in call. When Jisr refuses the token, the connector signs in again, so there is nothing to renew.

Organizations hosted in Saudi Arabia: if your Jisr address ends in .jisr.net.sa, your organization uses https://api.jisr.net.sa/api instead of https://apis.jisr.net/api. Change the connector's base URL and login URL to that host (login URL https://api.jisr.net.sa/api/openapi/v1/auth).

Employee data is personal data: employee records include dates of birth, personal contact data and document and passport numbers. Tick only the APIs you need on the key and share only what is needed. Bank details (IBAN) are removed from employee lists in any case; salaries stay hidden unless Get Employee Financial Info is ticked; custom fields come back only when the key has that permission.

Two employee identifiers: an employee has a public id (a UUID such as bab6cd98-7246-4cfc-a576-19bc00391792), used by jisr_get_employee and the attendance summary filter, and a numeric employee code (such as 43), used by punches and leave balances.

Dates and paging: dates are YYYY-MM-DD; punch times are date-times such as 2026-11-01T08:00:00. Without a range, the attendance summary covers the current month and the punch list the last hour. Lists return up to 100 entries per page (page from 1, rpp or limit); the AI keeps reading while data.pagination shows a next_page.

Common errors: This call requires login means the token expired, and the connector signs in again. Organization not found with given subdomain means JISR_SLUG is wrong. A refused sign-in means the slug, the API key or the secret is wrong: copy them again, or generate a new key if the secret was lost. A 403 means the API key lacks the permission for that API: edit the key under Settings → Webhook & API Keys and tick it.

Not covered: creating employees, payroll and accrual transactions, journals, webhooks and audit events.

What it reads: employees with public id and employee code, English and Arabic name, work and personal e-mail, phone, status, job title, department, location, business unit, employment type, nationality, line manager, joining date, date of birth, document and passport numbers, and termination and deletion dates, filtered by status or by creation, joining, termination or deletion date; one employee's full basic profile with personal details, address and contact data; attendance totals per employee for a period: working hours, late arrivals and early departures, extra working time, approved overtime, absence, days without records, leave days, off days, full-day excuses and business trip days; single punches with time, device serial number and, for rejected ones, the error Jisr reported; annual leave balances with opening and previous-year balance, manual adjustments, days used, pending and reserved days, unpaid leave deduction and year-end balance; the lists of departments, locations, employment types, business units, nationalities and outsourcing companies, with English and Arabic names.

Switched off at install: jisr_create_attendance_logs. It submits up to 100 attendance punches to Jisr, as a time clock or access-control system would; Jisr processes them in the background and they change employees' attendance records. Check the outcome afterwards with jisr_list_attendance_logs (status success or failed). If you need it, switch it on in the connector page; the AI asks you to confirm every change first. All other tools are read-only.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in ChatGPT

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

ChatGPT adds MCP servers as plugins on its Plugins page, on the web and on paid plans. Developer mode is no longer needed. In a Business workspace only admins and owners can add one; in Enterprise and Edu an admin can grant the Create plugins with MCPs permission.

1. Go to chatgpt.com/plugins, click Add, then Add custom MCP server.
2. Enter a name, e.g. Name: Jisr.
3. Under Connection, enter the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID and keep Authentication on OAuth.
4. Select I understand and want to continue, then Create as a plugin. When ChatGPT asks, sign in to AnythingMCP and allow access.
5. Install the new plugin from your personal plugins, then type @ in a chat and pick it.

Available tools

Example prompts

• "Who joined the company in the last 30 days, and in which department and location?"
• "Show me this month's attendance summary: who has the most late arrivals and absence days?"
• "Which punches did Jisr reject yesterday, and what error did it give for each?"
• "How many annual leave days are left for the employees with codes 43 and 77?"
• "List the employees offboarded this year, with their job title and termination date."

FAQ

Does the free ChatGPT plan work with custom MCP servers? OpenAI documents custom MCP servers for paid plans only; the Free plan is not on its list.

Next steps

• Connector landing page
• Connect to Claude