PayCaptain MCP connector
The PayCaptain connector brings employees, payslips, shifts and payments into Claude, ChatGPT and Cursor through one endpoint, so your team can ask about payroll and add new records inside their own PayCaptain access.
-
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 PayCaptain to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect PayCaptain once
-
Open Connections, choose Add connection, and pick PayCaptain.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a PayCaptain API key. One person generates a token in PayCaptain 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.
PayCaptain 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.
PayCaptain 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.
PayCaptain 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 PayCaptain 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 PayCaptain through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Payroll
Check who is on the payroll
Ask for the full PayCaptain employee list before a pay run closes and spot anyone missing or duplicated without scrolling through the app.
-
HR
Set up a new starter on day one
Create the new hire's PayCaptain employee record from the offer details, so they are ready for their first pay run before they have finished the tour.
-
Finance
Pull payslips for a reconciliation
List PayCaptain payslips for a period and check them against the ledger in one conversation instead of opening each one.
-
Operations
Log shifts as the rota changes
Add a shift in PayCaptain when someone covers extra hours, so the time reaches payroll without a spreadsheet in between.
-
Managers
Answer a pay question from the desk
Ask which PayCaptain payslips went out to your team this month and reply to the person with the facts, not a guess.
-
Payroll
Add an off-cycle payment
Create a PayCaptain payment for a bonus or an expense reimbursement so it lands in the next run without a separate form.
Try asking
- “Show me all PayCaptain employees added this quarter”
- “List this month's payslips for the warehouse team”
- “Add a Saturday shift for Priya Shah, 8am to 4pm”
AI tools
PayCaptain tools for your AI agents
5 tools are ready to call through Elaichi's MCP endpoint the moment you connect PayCaptain, 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 PayCaptain gets you
6 screens from the product, each doing one job for your PayCaptain account.
The agent
Ask about payroll, get answers from live records.
Three starter prompts pull PayCaptain employees, payslips and shifts into plain answers.
- employees
- payslips
- shifts
- payments
Ask Elaichi to work across your apps.
Show me all PayCaptain employees added this quarter
List this month's payslips for the warehouse team
Add a Saturday shift for Priya Shah, 8am to 4pm
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts PayCaptain in every AI client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
5 PayCaptain tools cover employees, payslips, shifts, payments.
Every resource and method is cataloged, with no custom code to write.
- List all PayCaptain employees
- Create a PayCaptain employee
- List all PayCaptain payslips
- Create a PayCaptain shift
Toolboxes
Each team gets its own PayCaptain toolbox.
Payroll, HR and Finance each work from a toolbox scoped to their job.
- Payroll
- HR
- Finance
- Operations
Shared connections
Teammates use PayCaptain without ever seeing the key.
One person connects, the table shows who shared it and with how many teams.
- Payroll UK
- HR
- Finance
- Warehouse ops
Audit log
Every PayCaptain call is written down.
When, who, what happened, type and resource, in an append-only log.
- 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 payroll digest itself.
Payslips are fetched, grouped, drafted into a digest, approved, then posted back to PayCaptain.
PayCaptain digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch employees
PayCaptain
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
PayCaptain
Queued
Collections and dashboards
PayCaptain health numbers arrive without asking.
Four metrics, 14 days of employees created and a team breakdown, refreshed on schedule.
PayCaptain health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Payslips
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
Payroll UK 34%
HR 27%
Finance 21%
Warehouse ops 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect PayCaptain to Claude?
Connect PayCaptain in Elaichi by pasting the API key from your PayCaptain account. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and PayCaptain is ready in your chats.
Does PayCaptain work with ChatGPT and Cursor as well as Claude?
Yes. Once PayCaptain 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 PayCaptain once and every client picks it up.
What can an AI agent actually do with my PayCaptain data?
Through Elaichi, an agent can list your PayCaptain employees, add a new employee, list payslips, add a shift and set up a payment. In practice that means asking who is on the payroll, pulling this month's payslips, or logging a shift from the conversation. Short, concrete asks such as "list payslips for March" work better than long sentences.
Does connecting PayCaptain give the AI everything in my payroll?
No. The AI only sees what the connected PayCaptain account can see, and only the people that connection is shared with can use it. Elaichi can narrow that further with roles and restrictions, and it never widens what PayCaptain itself allows.
Can I stop an agent from creating employees or payments in PayCaptain?
Yes. Restrictions in Elaichi work per action, so you can allow listing PayCaptain employees and payslips while blocking the creation of employees, shifts or payments. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.
What happens to a PayCaptain connection when someone leaves?
Offboarding the person in Elaichi ends their access to PayCaptain at once, in every client they used. A shared PayCaptain connection keeps working for everyone else on the team. If you disconnect PayCaptain once in Elaichi, it disappears from Claude, ChatGPT, Cursor and the Elaichi Agent together.
Does the PayCaptain MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. PayCaptain 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 PayCaptain 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.