hilan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMPANY_URL | No | The full Hilan tenant URL, e.g. https://amdocs.net.hilan.co.il. Highest priority for default tenant; used if set. | |
| COMPANY_CODE | No | Numeric Hilan org code, e.g. 5227. Used only if neither COMPANY_URL nor COMPANY_TENANT is set. | |
| HILAN_DB_KEY | No | The encryption key for the local database. Used if the OS credential store is not set up. Same trust model as any other API key/secret configured for an MCP server. | |
| COMPANY_TENANT | No | Bare Hilan tenant subdomain, e.g. amdocs. Used only if COMPANY_URL is not set. | |
| NODE_EXTRA_CA_CERTS | No | Path to your corporate CA bundle, for networks with TLS-intercepting proxies. Omit otherwise. | |
| HILAN_ENABLE_DEBUG_TOOLS | No | Set to '1' to enable debug/exploration tools (debugCallAsmx, debugDownloadPdf). Off by default. |
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 |
|---|---|
| dismissUpdateNoticeA | Call this after the user declines an update offered via an "_updateNotice" field on a previous tool response, passing that same version string, so hilan-mcp stops mentioning that specific version. It will still notify about a newer version later. |
| listTenantsA | List configured Hilan tenants (no secrets returned) |
| syncPayslipsA | Log into a Hilan tenant (using previously ingested credentials) and sync recent payslips (structured Bruto/Neto/parts + PDF) |
| downloadCombinedPayslipsPdfA | Downloads ONE PDF covering every payslip in a date range (instead of one file per month) — handy for printing/sharing a multi-year span at once. Automatically splits into multiple files for very long ranges (Hilan's combined-PDF endpoint has a practical ceiling of roughly 12-15 years per file due to a URL-length limit on their end). |
| getPersonalDetailsA | Logs in and fetches personal details (name, national ID, birthdate, address, phone, email, work start date, job type). This is a live lookup, not stored in the local database. |
| resyncPayslipMonthA | Re-fetch a single specific month (structured data, and by default the PDF too), overwriting whatever is already stored for it. Use this to retry one bad/truncated PDF, or to quickly check one month's numbers, instead of re-running syncPayslips over the whole history. |
| syncForm106A | Log into a Hilan tenant and download Form 106 (annual tax summary) for a given year, or the default year |
| listTablesA | List queryable tables (payslips, form106 — credentials/sessions are never exposed here) |
| describeTableA | Get columns and indexes for a table (payslips or form106 only) |
| queryA | Execute a SELECT-only SQL query against payslips/form106 (allowlisted; credentials/sessions/tenants are never reachable) |
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 10 tools
Most tools are clearly distinct, but syncPayslips and resyncPayslipMonth could be confused at a glance. Descriptions help disambiguate their scope, and the built-in querying tools (listTables, describeTable, query) are related but serve different purposes.
All tool names use camelCase and follow a verb-first pattern (sync, download, get, resync, list, describe, dismiss), but 'query' is a bare verb and 'dismissUpdateNotice' is verbose. Overall consistent, with a few minor deviations.
With 10 tools, the server is well-scoped. Each tool addresses a clear need for Hilan payroll integration, and none seem superfluous.
The tool surface covers core workflows: syncing payslips, downloading combined PDFs, retrieving personal details, and querying stored data. Missing operations like updating or deleting payslips are not typical for a read-only integration, but there's no explicit tool for managing credentials or tenants beyond listing them, which is a minor gap.