Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Paycor to Claude Code

Let Claude update employee records and stage pay runs in Paycor. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Paycor to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Paycor, you add a Paycor MCP server: a small hosted service that exposes Paycor's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Paycor account. No API keys pasted into config files.

claude mcp add --transport http paycor https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Paycor once connected?

Full read-write Paycor access lets Claude update employee profiles, submit time-off requests, change an employee status field, and stage payroll or pay-rate changes for your review. The HR data entry that used to mean clicking through screens or reconciling spreadsheets happens where the system of record already lives.

  • Update an employee profile field such as department, manager, or address
  • Submit a time-off request on an employee's behalf
  • Look up logged hours and time card punches for a pay period
  • Change the status field on an employee record
  • Stage payroll adjustments and flag them for your approval before a run
  • Pull a roster matching a query and propose batched record updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Paycor access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Paycor API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Paycor changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Paycor connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Paycor connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Paycor account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Paycor's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Paycor?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Paycor account it signs in with. Revoking access is one click in Paycor.

More on the Paycor connector

Paycor connector for claude.aiDeel + Claude CodeJustworks + Claude CodePaychex + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us