salik-hr-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
salik-hr-mcp
The MCP protocol server for the Salik Labs HR app — a separate service from the main
salik-hr Next.js app, by design. See docs/MCP_SERVICE_SPLIT.md in the salik-hr repo
for the full design and why this split exists; docs/MCP_PLAN.md there covers the tool
inventory and product scope, still accurate here.
What this is
A thin, stateless protocol layer:
No database. No Drizzle, no schema, no employee data model.
No business logic. Every rule (who can approve what, balance checks, the CEO auto-approve behavior, the sign-off visibility rule) lives in the main app and is enforced there — this service cannot bypass it, because it never has more access than the bearer token it was handed.
Every tool call is a
fetch()to${HR_APP_BASE_URL}/api/..., forwarding the caller's own token onAuthorization: Bearer. The main app'smiddleware.tsverifies that token and resolves identity — this service trusts it to do that correctly and does no verification of its own beyond oneGET /api/me/sessioncall per connection, to know which tools to register (write tools only for aread_write-scope token).
Related MCP server: successfactors-mcp-prototype
Local development
npm install
cp .env.example .env.local
# edit .env.local: HR_APP_BASE_URL=http://localhost:3000 (the main app's dev server)
npm run devRequires the main app (salik-hr) running locally with a minted personal access token
(mint one at /me → Connected apps, once signed in as a role MCP_TOKEN_ROLES allows).
Connecting a client
Point any MCP client at http://localhost:8787/mcp (or the deployed URL) with
Authorization: Bearer <your slhr_ token>. Example, Claude Code:
claude mcp add --transport http salik-hr http://localhost:8787/mcp \
--header "Authorization: Bearer $SALIK_HR_TOKEN"Deployment
Deploy as its own service (its own Railway service, or any Node host) with
HR_APP_BASE_URL pointed at the main app's production URL. npm run build && npm start.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
Unofficial remote MCP server for Less Annoying CRM: OAuth 2.1, read-only grants, 10 tools.
Hosted MCP for Google Workspace, Atlassian and Notion: one OAuth, per-user accounts, write access.
Discover, plan and run tools across your connected business systems through one OAuth MCP endpoint
Related MCP Servers
- FlicenseAqualityDmaintenanceRead-only MCP server for the Tipsoi HRM API, exposing 15 tools to read employee data, attendance, leave, overtime, and more.153-
- FlicenseNot gradedqualityDmaintenanceEnables answering authorized HR questions by exposing a set of read-only MCP tools over synthetic SuccessFactors-style data, with optional AI agent orchestration and configurable modes for mock, demo, or real test tenant usage.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to securely access Onyx search, chat, agents, projects, documents, connectors, ingestion, and deployment-specific APIs through configurable tool profiles.47 npmMIT
- AlicenseAqualityAmaintenanceEnables MCP clients to securely access Jisr's documented HR Open API read-only operations, including employees, attendance, leave, payroll, finance, and discovery tools, with role-based field policies and dual protocol support.11MIT