jisr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JISR_SLUG | Yes | Your organization slug. | |
| JISR_API_KEY | Yes | Your Jisr API key. | |
| JISR_BASE_URL | Yes | The base URL for the Jisr API. Use https://apis.jisr.net/api for AWS-hosted or https://api.jisr.net.sa/api for locally hosted. Any other host is rejected at startup. | |
| JISR_API_SECRET | Yes | Your Jisr API secret. | |
| JISR_MCP_ADAPTER | No | Set to 'mcp-v1' to use the v1 protocol adapter instead of the default v2 adapter. | mcp-v2 |
| JISR_ROLE_PROFILE | Yes | The role profile that determines which tools are available. One of: employee_self, manager, hr_operations, finance, integration_admin, auditor, platform_operator. | |
| JISR_FINANCE_API_KEY | No | Optional, recommended finance-scoped API key for the finance surface. | |
| JISR_FINANCE_SURFACE | No | Set to 'enabled' to expose the financial tools. Requires JISR_ROLE_PROFILE=finance. Otherwise the finance tools are hidden. | |
| JISR_FINANCE_API_SECRET | No | Optional, recommended finance-scoped API secret for the finance surface. | |
| JISR_SUBJECT_EMPLOYEE_ID | No | The employee UUID required when JISR_ROLE_PROFILE is employee_self or manager. The server refuses to start without it for these profiles. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jisr_connection_status_getA | Reports whether this server can reach Jisr, when it last authenticated, and the last authentication error if any. Returns no credentials or organization identifiers. |
| jisr_capabilities_getA | Lists every documented Jisr operation and, for each, four independent facts: whether the specification supports it, whether the connected API key permits it, whether your role allows it, and whether the operator enabled it. Explains why anything unavailable is unavailable, and who can change that. |
| jisr_departments_listA | Lists the organization's departments, each with its identifier and both English and Arabic names. Use these to resolve names to stable identifiers before filtering other tools. |
| jisr_employment_types_listA | Lists the organization's employment types, each with its identifier and both English and Arabic names. Use these to resolve names to stable identifiers before filtering other tools. |
| jisr_business_units_listA | Lists the organization's business units, each with its identifier and both English and Arabic names. Use these to resolve names to stable identifiers before filtering other tools. |
| jisr_locations_listA | Lists the organization's locations, each with its identifier and both English and Arabic names. Use these to resolve names to stable identifiers before filtering other tools. |
| jisr_nationalities_listA | Lists the organization's nationalities, each with its identifier and both English and Arabic names. Use these to resolve names to stable identifiers before filtering other tools. |
| jisr_outsourcing_companies_listA | Lists the organization's outsourcing companies, each with its identifier and both English and Arabic names. Use these to resolve names to stable identifiers before filtering other tools. |
| jisr_webhooks_listA | Lists the organization’s webhook subscriptions: name, endpoint, HTTP method, status and subscribed events. Stored authentication material is never returned. |
| jisr_audit_events_listA | Lists Jisr audit events, filterable by module, event name, event type and date range. Filters are ordinary named inputs; the server encodes them into Jisr’s bracketed query syntax. |
| jisr_data_catalog_getA | Describes the available Jisr domains: which tools serve them, what classified field groups each tool may return and why, how pagination works, and how fresh the data is. Returns no records. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool maps to a distinct resource: connection status, capabilities, seven reference-data lists, webhooks, audit events, and data catalog. The similar list tools are clearly separated by entity type, and the two metadata tools serve different purposes.
All tool names follow the same jisr_<resource>_<verb> pattern, using consistent snake_case and terminal _get or _list verbs. There is no mixing of conventions or vague generic verbs.
Eleven tools is well within the ideal range for a domain-specific MCP server. Each tool earns its place, covering reference data, metadata, and system visibility without unnecessary overlap.
The server thoroughly covers organizational reference data, capabilities, webhooks, and audit events, but it is almost entirely read/list-oriented. It lacks tools for core organizational entities beyond reference data, such as employees, and provides no create/update/delete operations, leaving notable gaps for broader Jisr workflows.