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.
- Connects with an API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Show me all PayCaptain employees added this quarter
Working in PayCaptain with Elaichi
-
List all PayCaptain employees
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect PayCaptain to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
PayCaptain MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with PayCaptain through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in PayCaptain is logged.
-
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”
What connecting PayCaptain gets you
6 screens from Elaichi, each doing one job for your PayCaptain account.
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, Cursor or Microsoft Copilot
The agent
Ask about payroll, get answers from live records.
Three starter prompts pull PayCaptain employees, payslips and shifts into plain answers.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
One endpoint puts PayCaptain in every AI client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
5 PayCaptain tools cover employees, payslips, shifts, payments.
Every resource and method is cataloged, with no custom code to write.
ElaichiToolboxesToolboxes
Each team gets its own PayCaptain toolbox.
Payroll, HR and Finance each work from a toolbox scoped to their job.
ElaichiConnectionsShared connections
Teammates use PayCaptain without ever seeing the key.
One person connects, the table shows who shared it and with how many teams.
ElaichiAudit logAudit log
Every PayCaptain call is written down.
When, who, what happened, type and resource, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
PayCaptain digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
PayCaptain
Queued
Workflows
A schedule starts the payroll digest itself.
Payslips are fetched, grouped, drafted into a digest, approved, then posted back to PayCaptain.
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%
Collections and dashboards
PayCaptain health numbers arrive without asking.
Four metrics, 14 days of employees created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for PayCaptain
All three can connect PayCaptain 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 PayCaptain tools | Allow or restrict single PayCaptain 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 PayCaptain 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting the creation of employees, shifts or payments. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 PayCaptain?
Yes. Both let Claude, ChatGPT or Cursor use PayCaptain. 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 PayCaptain call.
How is Elaichi different from Composio for PayCaptain?
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 PayCaptain: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put PayCaptain in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot