Skip to content

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. 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 TriNet to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect TriNet once

  1. Open Connections, choose Add connection, and pick TriNet.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a TriNet API key. One person generates a token in TriNet 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.

trinet
TriNet
360learning
7shifts
Altera Payroll
BambooHR
Dayforce
2

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. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 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. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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”

See all 61 TriNet tools below

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.

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 clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

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
ElaichiTools
Tool Action Description
Create a TriNet employee Create Add Employee (TriNet POST /v1/hire/{{company_id}}/employee). Takes no caller parameters. The companyId comes from the connection credential. Requires a JSON request body; TriNet does not publish the request schema, so no body_schema row exists. Vendor gaps: TriNet publishes no query or paging parameters for any endpoint, and no per-endpoint 200 schema, so `response_path` (`data`) is taken from TriNet's generic response envelope and is UNVERIFIED.
List all TriNet employees List List All Employees (TriNet GET /v1/company/{{company_id}}/employees). Takes no caller parameters. The companyId comes from the connection credential. Vendor gaps: TriNet publishes no query or paging parameters for any endpoint, and no per-endpoint 200 schema, so `response_path` (`data`) is taken from TriNet's generic response envelope and is UNVERIFIED. Beyond the general `read` scope, seven section scopes control which sections of this response are returned: `basic-read` -> departmentSplit, employementInfo, names; `hr-personal-read` -> emergencyContacts, homeAddress, employeeContacts, workEligibility; `hr-bioinfo-read` -> bioInfo; `hr-admin-read` -> customFields; `hr-pay-read` -> payInfo; `hr-security-read` -> roles; `hr-natid-read` -> nationalIds. (`employementInfo` is TriNet's own spelling.) A credential holding only `read` still succeeds, with fewer sections.
Get single TriNet citizenship by ID Get Get Citizenship (TriNet GET /v1/profile/{{company_id}}/{{id}}/citizenship). Caller must supply `id`. The companyId comes from the connection credential. Vendor gaps: TriNet publishes no query or paging parameters for any endpoint, and no per-endpoint 200 schema, so `response_path` (`data`) is taken from TriNet's generic response envelope and is UNVERIFIED.
TriNet custom fields bulk update Update Update Custom Fields (TriNet PUT /v1/manage-employee/{{company_id}}/{{query.employee_id}}/custom-fields). Caller must supply `employee_id`. The companyId comes from the connection credential. Requires a JSON request body; TriNet does not publish the request schema, so no body_schema row exists. Vendor gaps: TriNet publishes no query or paging parameters for any endpoint, and no per-endpoint 200 schema, so `response_path` (`data`) is taken from TriNet's generic response envelope and is UNVERIFIED.
Get single TriNet department split by ID Get Department Split (TriNet GET /v1/department/{{company_id}}/{{id}}/department-split). Caller must supply `id`. The companyId comes from the connection credential. Vendor gaps: TriNet publishes no query or paging parameters for any endpoint, and no per-endpoint 200 schema, so `response_path` (`data`) is taken from TriNet's generic response envelope and is UNVERIFIED.

Toolboxes

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
ElaichiToolboxes
Name Source template Tools Created

HR toolbox

TriNet · employees and emergency contacts

TriNet starter 18 Mar 4, 2026

People Ops toolbox

TriNet · custom fields and personal details

— 9 Mar 2, 2026

Managers toolbox

TriNet · supervisors and jobs

— 24 Feb 27, 2026

IT toolbox

TriNet · employee roles and account setup

TriNet starter 6 Feb 19, 2026

Finance toolbox

TriNet · department splits and employment details

— 31 Jan 30, 2026

Workplace toolbox

TriNet · addresses and contacts

— 12 Jan 22, 2026

Shared 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
ElaichiConnections
Connection Scope Status Access
TR

TriNet (HR)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
TR

TriNet (People Ops)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
TR

TriNet (Managers)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
TR

TriNet (IT)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
TR

TriNet (Payroll)

Connected by Clara Nowak

Personal • Active Not shared
TR

TriNet (Workplace)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit 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 log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

TriNet Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

TriNet Employees Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

TriNet Employees List Toolbox

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, 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 Emma Laurent

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch employees

    TriNet

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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%

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 my team share one TriNet connection?

Yes. One person connects TriNet with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so the audit log names the actual person behind every TriNet lookup or change.

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.

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
Claude ChatGPT Cursor 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.