TriNet MCP connector
The TriNet connector brings employees, emergency contacts, jobs, supervisors and employment details into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update people records inside their own TriNet access, with every change logged.
-
How it connects. App credentials. 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.
61 tools
How to connect
How to connect TriNet to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect TriNet once
-
Open Connections, choose Add connection, and pick TriNet.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your TriNet app credentials. TriNet authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
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.
TriNet 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.
TriNet 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.
TriNet 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 TriNet 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 TriNet 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 one go
Create the employee in TriNet, add their name, contact details and emergency contact, and confirm it all landed without clicking through five screens.
-
HR
Keep emergency contacts current
Ask which employees have no emergency contact on file, then update the missing ones in one pass after the annual reminder goes out.
-
People Ops
Fill in custom fields across the company
When a new field such as a badge number or preferred name is added, update it for a whole group of employees at once instead of one record at a time.
-
Managers
See who reports to whom
Pull the list of supervisors, jobs and employee roles for a department and get a plain answer about the reporting line before a reorg conversation.
-
IT
Get the employee list for account setup
List active employees with their employment details and jobs so new accounts, hardware and licenses match what TriNet says on day one.
-
Workplace
Check addresses before shipping equipment
Look up an employee's address and contact details in TriNet before sending a laptop or welcome kit, and catch a stale address before the courier does.
Try asking
- “List employees who joined this month with their supervisors”
- “Which employees are missing an emergency contact?”
- “Add Priya Shah as a new employee in Customer Success”
Compare
Elaichi vs Zapier MCP vs Composio for TriNet
All three can connect TriNet to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over TriNet tools | Allow or restrict single TriNet tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per TriNet call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
TriNet tools for your AI agents
61 tools are ready to call through Elaichi's MCP endpoint the moment you connect TriNet, 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 TriNet gets you
6 screens from the product, each doing one job for your TriNet account.
The agent
Ask about employees, get answers from TriNet.
Plain language questions return live TriNet employees, supervisors and emergency contacts.
- employees
- emergency contacts
- contacts
- jobs
Ask Elaichi to work across your apps.
List employees who joined this month with their supervisors
Which employees are missing an emergency contact?
Add Priya Shah as a new employee in Customer Success
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts TriNet in every client.
Claude, ChatGPT and Cursor reach TriNet through one governed endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
61 TriNet tools, nothing to build.
Employees, contacts, jobs, addresses and custom fields covered without writing any code.
- Create a TriNet employee
- List all TriNet employees
- Get single TriNet citizenship by ID
- TriNet custom fields bulk update
ElaichiToolsToolboxes
Each team gets its own TriNet toolbox.
HR, managers and IT each work from a toolbox scoped to their job.
- HR
- People Ops
- Managers
- IT
ElaichiToolboxesShared connections
Teammates use TriNet without holding the key.
One person connects TriNet, shares it, and nobody else ever sees a credential.
- HR
- People Ops
- Managers
- IT
ElaichiConnectionsAudit log
Every TriNet change names who made it.
When, who, what happened and which employee record, kept in one append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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, a person approves.
New TriNet employees are fetched, grouped, drafted into a digest, approved, then posted back.
TriNet digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch employees
TriNet
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
TriNet
Queued
Collections and dashboards
TriNet headcount numbers, computed without a model.
Four metrics, fourteen days of employees created, a team breakdown, refreshed on schedule.
TriNet health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Emergency contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
HR 34%
People Ops 27%
Managers 21%
IT 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect TriNet to Claude?
Connect TriNet in Elaichi first: paste in the API key from your TriNet account and Elaichi takes it from there, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Sign in as yourself and TriNet employees, contacts and jobs are available in your next conversation.
Does TriNet work with ChatGPT and Cursor as well as Claude?
Yes. Once TriNet 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 TriNet once and every client you use picks it up.
What can an AI agent actually do with my TriNet data?
With TriNet connected, an agent can list employees, look up a person's job, supervisor, address, employment details and biographical details, and pull up photos and company org details. It can also create a new employee, add names, contacts and emergency contacts, and update contacts, names, personal details and custom fields for many employees at once. Short, concrete asks work best, such as "list employees in Finance with their supervisors".
Does connecting TriNet give the AI access to every employee record?
No. Every request to TriNet runs inside the access of the person who signed in, so someone who cannot see a record in TriNet cannot see it through an agent either. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what TriNet already allows that person.
Can I stop an agent from changing employee records in TriNet?
Yes. In Elaichi you restrict TriNet actions individually, so you can allow looking up employees while blocking the creation of employees or the bulk update of contacts, names or custom fields. A restricted action is never shown to Claude, ChatGPT or any other client at all, so no prompt can reach it.
What happens to a TriNet connection when someone leaves?
Offboarding a person in Elaichi ends their access to TriNet through every client at once. If they had shared a TriNet connection with a team, it keeps working for everyone else. Disconnecting TriNet once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the TriNet MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. TriNet 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.
Is Elaichi an alternative to Zapier MCP for TriNet?
Yes. Both let Claude, ChatGPT or Cursor use TriNet. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every TriNet call.
How is Elaichi different from Composio for TriNet?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to TriNet: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put TriNet 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.