Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Deel to Claude Code

Have Claude draft contracts and update worker records in Deel. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Deel to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Deel, you add a Deel MCP server: a small hosted service that exposes Deel'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 Deel account. No API keys pasted into config files.

claude mcp add --transport http deel 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 Deel once connected?

Full read-write Deel access lets Claude draft and send contracts, add or update worker and team records, submit payroll inputs and off-cycle payments for your review, and manage onboarding tasks once you confirm. Final approval and payment stay in Deel's UI. The HR and payroll work that used to mean tabbing between Deel and a spreadsheet happens where the data already lives.

  • Draft and send a contractor or EOR contract from a role and rate you specify
  • Add a new worker and update profile, team, or compensation fields
  • Submit payroll inputs like bonuses, deductions, and off-cycle payments for review
  • Create and assign onboarding tasks for a new hire
  • Update time off, expense, or invoice statuses as you review them
  • Find every worker 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 Deel 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 Deel API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Deel 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 Deel 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 Deel 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 Deel 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 Deel'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 Deel?
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 Deel account it signs in with. Revoking access is one click in Deel.

More on the Deel connector

Deel connector for claude.aiJustworks + Claude CodePaychex + Claude CodePaycor + 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