Skip to main content
Glama
nikulk2992-jpg

prismhr-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PRISMHR_MCP_PEO_IDNoPrismHR PEO ID (direct auth).
PRISMHR_MCP_PASSWORDNoPrismHR API password (direct auth).
PRISMHR_MCP_USERNAMENoPrismHR API username (direct auth).
PRISMHR_MCP_ALLOW_PRODNoSet to 'true' to allow production environment. Default: false.false
PRISMHR_MCP_ENVIRONMENTNoEnvironment (uat or prod). Default: uat.uat
PRISMHR_MCP_ONEPASSWORD_VAULTNo1Password vault name for credential retrieval.
PRISMHR_MCP_ONEPASSWORD_ITEM_PRISMHRNo1Password item name containing PrismHR credentials.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
meta_pingA

Health check. Returns server name, version, and UTC time.

Always callable — no scope required. Use this to confirm the server is reachable before worrying about credentials or permissions.

meta_aboutA

Describe what this MCP server is, who runs it, and what commercial options exist.

Always callable — no scope required. Surfaces commercial offerings (Solution Architect white-label, Enterprise support) so Claude can help users understand what's available beyond the free OSS core.

meta_request_permissionsA

List every scope the server can request, grouped by category.

Returns: the full manifest, which scopes are currently granted, the server's recommended defaults (reads = yes, writes = no), and a human-readable message to show the user. Call meta_grant_permissions next with the scopes the user approves.

meta_grant_permissionsA

Grant, revoke, or replace the set of scopes this server may use.

Prerequisite scopes are auto-included: granting 'employee:read' also grants 'client:read' because the search tool needs it. Revoking a prerequisite cascades — dependent scopes get dropped to stay consistent.

meta_list_permissionsA

Show the currently granted scopes without the full manifest.

Use this when you just want to know what's active right now. Use meta_request_permissions to see the full catalog.

meta_upstream_permissionsA

Ask PrismHR which API methods this account is actually allowed to call.

Calls /login/v1/getAPIPermissions. If the account lacks a method, even a fully-scope-granted MCP tool will 403 at the PrismHR edge. Use this to diagnose 'permission denied' errors when meta_list_permissions shows the scope is granted.

Always callable — no scope required.

meta_capabilitiesA

What does this server know how to call against PrismHR?

Returns counts (catalog size, verified, admin-blocked, unprobed) and a sample of callable methods. Use this when the user asks 'what can you do?' or before picking a specific method via meta_describe.

meta_describeA

Full contract for a single PrismHR method.

Returns every parameter, inline body schema (when available), response codes, and verification status. Call this before prismhr_call so you know exactly which args the method wants.

meta_findA

Find PrismHR methods by intent.

Use when you don't know the exact method id. Claude should pick the best hit + follow up with meta_describe to see the contract.

meta_callA

Generic, schema-validated invocation of any PrismHR method in the catalog.

Pre-flight: checks the method_id, refuses admin services, validates required query + header + body fields against the bundled bible schemas. Only after validation passes does the request hit PrismHR.

Every call returns a structured PrismHRCallResponse — ok | prismhr_error | validation_error | admin_blocked | unverified_warning. The unverified_warning status is attached when the call succeeds but the response shape has not been verified by the maintainer's probe pass; treat the body as best-effort.

client_listA

List every client the current PEO account can see.

Use when the user says "show me the clients" or "which companies are on our platform". Returns each client's ID, name, and active status. Most other tools need a client ID, so call this first when you don't have one.

client_employeesA

List the employees at a single client.

Use when the user says "who works at Acme" or "show me active employees at client XYZ". Returns each employee's ID, name, work email, hire date, and status.

client_employeeA

Pull full profile detail for one or more employees.

Use when the user asks "show me John's full record" or "get details on these five employees at Acme". Returns the complete employee profile: name, hire/termination dates, pay group, status, and the termination reason if applicable.

client_employee_searchA

Find an employee by name or email, across every client at once.

Use when the user says "find Jane Doe" or "is there anyone named Smith in our system" without knowing which client they're at. Slow path because it walks every client, so prefer client_employees when you already know the client.

payroll_batch_statusA

Find the payroll batches a client ran in a date window.

Use when the user asks things like "what payrolls ran at Acme in March" or "show me this quarter's batches for client ABC". Returns batch IDs, pay dates, status, voucher counts, and gross totals.

payroll_pay_historyA

Get an employee's paychecks in a date window, plus year-to-date totals.

Use when the user asks "what did Jane get paid this quarter" or "pull up John's checks for Q1". Returns each paycheck (gross, net, regular/overtime hours) plus YTD gross/net/taxes.

payroll_pay_group_checkA

Check whether an employee is set up to be paid (pay group assigned).

Use when the user asks "why didn't Jane get paid" or "is this new hire ready for payroll". Returns whether a pay group is assigned and the pay frequency (weekly/biweekly/etc). Unassigned pay group is the #1 reason an employee is skipped in a payroll run.

payroll_superbatch_statusA

Summarize a client's payroll cycle health across a date range.

Use for morning-of-pay status checks: "how's Acme's payroll looking this week" or "show me everything that's open vs. posted for client XYZ this quarter". Counts batches by status (open / pending / posted / voided) and totals gross payroll across them.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikulk2992-jpg/prismhr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server