# 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. Source: https://elaichi.ai/connectors/paycaptain/ ## Facts | | | | --- | --- | | Application | PayCaptain | | Category | HRIS | | AI tools | 5 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once PayCaptain is connected - 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 ## Connect PayCaptain in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick PayCaptain. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which PayCaptain tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## PayCaptain MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect PayCaptain to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a PayCaptain tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with PayCaptain through Elaichi ### Check who is on the payroll Payroll. Ask for the full PayCaptain employee list before a pay run closes and spot anyone missing or duplicated without scrolling through the app. ### Set up a new starter on day one HR. 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. ### Pull payslips for a reconciliation Finance. List PayCaptain payslips for a period and check them against the ledger in one conversation instead of opening each one. ### Log shifts as the rota changes Operations. Add a shift in PayCaptain when someone covers extra hours, so the time reaches payroll without a spreadsheet in between. ### Answer a pay question from the desk Managers. Ask which PayCaptain payslips went out to your team this month and reply to the person with the facts, not a guess. ### Add an off-cycle payment Payroll. Create a PayCaptain payment for a bonus or an expense reimbursement so it lands in the next run without a separate form. ## 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 my team share one PayCaptain connection? Yes. One person connects PayCaptain 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 to Elaichi as themselves, so the audit log names the person behind every PayCaptain call. ### 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. ## All 5 PayCaptain tools Every tool below is callable through https://api.elaichi.ai/mcp once PayCaptain is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all PayCaptain employees** (List). Get employees, paginated at 50 records per page. Returns: company, hrEmployeeId, payrollCode, firstName, middleName, lastName, dateOfBirth, gender. Optional filters: lastModifiedDate, includeFormer. company comes from the connected credential. - **Create a PayCaptain employee** (Create). Create or update an employee. - **List all PayCaptain payslips** (List). Get all payslips and payslip lines for one pay period, paginated at 50 records per page. Returns: payslip, employee, totals, ytd, previousEmployment, thisEmployment, payslipLines. Required: payPeriod. No PayCaptain endpoint enumerates valid pay periods, so that value must come from out of band. company comes from the connected credential. - **Create a PayCaptain shift** (Create). Create, update, or archive a shift in PayCaptain by submitting the shift dataset as a JSON request body. Returns a success response with no documented response body content. - **Create a PayCaptain payment** (Create). Create, update, or archive a payment in PayCaptain by submitting the payment dataset. Returns a 200 Success response with no documented response body.