Proliant MCP connector
The Proliant connector brings employees, dependents, pay rates and accrual balances into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update Proliant records inside their own access, with every change logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Proliant to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Proliant once
-
Open Connections, choose Add connection, and pick Proliant.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Proliant API key. One person generates a token in Proliant and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Proliant MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Proliant MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Proliant MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Proliant to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Proliant through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
HR
Set up a new hire in Proliant
Create the employee record from the offer details, then attach dependents and a starting pay rate without leaving the conversation.
-
Payroll
Fix a pay rate before the run closes
Pull up an employee's current rates, correct the one that is wrong, and read it back to confirm before payroll locks.
-
Payroll
Apply an annual raise across a whole team
Update rates in bulk for everyone on a list, then check the new figures to make sure nobody was missed.
-
Benefits
Update dependents after a life event
When someone marries or has a child, add or update the dependent in Proliant from the details they sent over.
-
Finance
Check accrual balances before approving leave
Ask how much paid time off an employee has accrued and see which company accrual plan it comes from.
-
Operations
Answer headcount questions across every company
List employees for any Proliant company you manage and get a plain answer on who is active where.
Try asking
- “Show Maria Lopez's current pay rates and accrual balance”
- “List every employee added to Acme Holdings this month”
- “Add a dependent for James Park, spouse, born 1988”
AI tools
Proliant tools for your AI agents
233 tools are ready to call through Elaichi's MCP endpoint the moment you connect Proliant, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Proliant gets you
6 screens from the product, each doing one job for your Proliant account.
The agent
Ask about employees and rates in plain language.
Answers come from live Proliant records, not a stale export.
- employees
- dependents
- rates
- accruals
Ask Elaichi to work across your apps.
Show Maria Lopez's current pay rates and accrual balance
List every employee added to Acme Holdings this month
Add a dependent for James Park, spouse, born 1988
Also runs in Claude, ChatGPT or Cursor
MCP clients
One governed endpoint, every client, no shared key.
Claude, ChatGPT and Cursor reach Proliant through one org endpoint, no SDK required.
Copy the endpoint
Tool catalog
233 Proliant tools, no code to write.
Employees, dependents, rates and accruals covered end to end, ready the moment you connect.
- List all Proliant companies
- Get single Proliant company by ID
- List all Proliant employees
- Create a Proliant employee
Toolboxes
Every team gets its own Proliant toolbox.
Payroll, HR and Benefits each work from a toolbox scoped to their job.
- HR
- Payroll
- Benefits
- Finance
Shared connections
Share one Proliant connection, never the key.
See who connected each account and which teams and members work through it.
- HR
- Payroll
- Benefits
- Finance
Audit log
Know who changed every rate and record.
Every Proliant call is logged with who, when, what happened and which resource.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the work, you approve it.
New Proliant employees are fetched, grouped, drafted into a digest, approved, then posted back.
Proliant digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch employees
Proliant
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Proliant
Queued
Collections and dashboards
Proliant health numbers, computed without a model.
Four metrics, 14 days of employees created and a team breakdown, refreshed on schedule.
Proliant health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Dependents
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
HR 34%
Payroll 27%
Benefits 21%
Finance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Proliant to Claude?
Connect Proliant in Elaichi first: Proliant connects with an API key, so you paste the key from your Proliant account into Elaichi and the connection is live. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and the whole thing takes a few minutes.
Does Proliant work with ChatGPT and Cursor as well as Claude?
Yes. Once Proliant is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Proliant once and every client picks it up.
What can an AI agent actually do with my Proliant data?
It can look up companies, employees, dependents, pay rates and accrual balances in Proliant, and answer questions about them in plain language. It can also create a new employee, add a dependent, change or bulk update pay rates, and adjust accruals when you ask. Short, concrete asks such as "show Maria's current pay rates" work better than long paragraphs.
Does connecting Proliant give the AI access to every employee and company?
No. Every call runs as the person who signed in, so the AI sees only the Proliant companies and employee records that person's access already allows. Elaichi can narrow that further for a team, but it never widens what someone could see in Proliant on their own.
Can I stop an agent from deleting or changing things in Proliant?
Yes. Restrictions in Elaichi work per action, so you can allow reading employees and rates while blocking the actions that delete an employee or change a pay rate in Proliant. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Proliant connection when someone leaves?
Offboarding a person in Elaichi ends their access to Proliant through every client at once. A shared Proliant connection keeps working for everyone else on the team. If you disconnect Proliant in Elaichi, it disappears from Claude, ChatGPT, Cursor and the Elaichi Agent in one step.
Does the Proliant MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Proliant is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Proliant in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.