Automation

[ welcome ] [ Developer ]

get started

Everything in Remote is reachable through the interface that best matches how you build.
APICLIMCPSandbox

Access a sandbox preloaded with employees, contracts, payroll, and expenses. Test your connectors, including API calls, CLI workflows, and integrations, on realistic data without touching production.

Choose the surface that fits {{your work}}

for durable integrations

Build integrations that last

Get started with the CLI
  • Automate scheduled workflows
  • Connect Remote to HR, finance and analytics platforms
  • Common use cases
https://developer.remote.com/docs/getting-started ↗

The API, CLI and MCP are designed to work together.

Better together

Better{{together}}

Employees, contracts, payroll, expenses — sample data that lets you test API calls, CLI commands, and integrations without risking actual records.

Build on Remote — Request a sandbox

01
Try connector workflows, debug integrations, validate commands. Every test runs on sandbox data.

Use realistic data

02
Request access, sign in, start testing.

Experiment freely

03
Test our connectors {{today}}

Get started now.

$ remote sandbox --init

or get started with

Explore without setup

Build surfaces
You sign in. That's it. The authentication, the permissions, and the compliance posture all carry over.

Sign in through your browser or use an API token, the same way you log into Remote. We don't ask you to generate API keys or store secrets, and your credentials never touch the tool you're using.is as
secureas logging in

Connecting to Remote is as secure {{as logging in}}

⌐Whatever permissions you have in Remote, you have through the CLI/API/MCP. An employee sees employee data, an admin sees employer data, and nothing more.
{soft}secure{/soft} {jolt}auth{/jolt}

OAuth 2.0 / Secure Auth

◈The CLI/API/MCP expose specific, structured endpoints, not raw database access. Remote controls what's returned, so you receive clean data rather than bulk exports or unstructured dumps.
{soft}inherited{/soft} {jolt}RBAC{/jolt}

Inherited RBAC

⊟Remote sends only what you request, and only to the tool or agent you've authorised. Your workforce data is not used to train any AI provider's models.
{soft}governed{/soft} {jolt}endpoints{/jolt}

Governed endpoints

◎The CLI, API, and MCP operate under Remote's existing security and compliance framework, with the same rigour you already trust.
{soft}privacy{/soft} {jolt}data use{/jolt}

Your data stays your data

◉Connecting&#32;<br>to Remote
{jolt}SOC 2 Type II{/jolt} {soft}certified{/soft}

SOC 2 Type II certified

Whether you are embedding Remote, developing integrations, or adding AI features, Remote supplies the appropriate interface for each workflow. The API supports durable integrations, the CLI accelerates team workflows and operations, and MCP makes Remote accessible to AI agents.

Like Personio, BambooHR, and others, you provide global employment for your customers through Remote. The CLI enables your team to trial workflows in sandbox, troubleshoot problems, and perform operational tasks more quickly—reducing implementation time and improving support.

Build products {{on Remote}}

01Embedded partners
Continue building on Remote's public API for the durable integrations you've developed. The CLI helps your team test endpoints, validate workflows, and diagnose issues more quickly.

EMBEDDED

02Integration partners
read the docs ↗

INTEGRATION

All three surfaces (API, CLI, MCP) support flexible authentication. Whether you're scripting, building an integration, or attaching an AI tool, authentication is straightforward and secure. No API keys to rotate. No secrets to retain. Your Remote permissions apply across every surface.

For individual users signing in via a browser (CLI, MCP).

Authentication that works across {{every interface}}

01
For direct customer scripts and backend automation.

OAuth 2.0

02
For partner integrations.

API tokens

03
get started

Client credentials

https://developer.remote.com/docs/

© Remote · Build on Remote

Ready to connect? {{It takes minutes to set up}}

R#get-startedhttps://developer.remote.com/docs/getting-started-with-remote
API · CLI · MCP · SandboxBuild production integrations with the API, use the CLI for operational tasks, and connect MCP when you want AI to interact with your workforce data. Most teams combine all three.