Everything in Remote is accessible via the interface that best suits how you build.
The Remote API is made for production. Build reliable integrations that sync workforce data, automate business processes, and power applications over the long term.
The Remote CLI speeds up everyday tasks. Manage your workforce, automate recurring jobs, and access Remote without leaving the terminal.
Link ChatGPT, Claude, Cursor, or any MCP-compatible client to Remote. Query live workforce data, automate workflows, and create AI assistants that understand your organisation.
The API, CLI, and MCP are built to work together.
Build production integrations with the API, use the CLI for operational tasks, and connect MCP where AI needs to interact with your workforce data. Most teams combine all three.
Employees, contracts, payroll, expenses — sample data that lets you test API calls, CLI commands, and integrations without risking real records.
Try connector workflows, debug integrations, and validate commands. Every test runs on sandbox data.
Request access, sign in, and start testing.
$ remote sandbox --init
Access a sandbox preloaded with employees, contracts, payroll, and expenses. Test your connectors, including API calls, CLI workflows, and integrations, using realistic data without touching production.
You sign in. Authentication, permissions, and the compliance posture then carry across.
Sign in through your browser or use an API token, the same method you use to log into Remote. You won’t need to create API keys or store secrets, and your credentials never reach the tool you use.
The permissions you hold in Remote apply to the CLI, API, and MCP. An employee can access employee data, an admin can access employer data, and nothing beyond that.
The CLI, API, and MCP provide defined, structured endpoints rather than direct database access. Remote governs the responses, so you receive tidy data without bulk exports or unstructured dumps.
Remote transmits only the data 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.
The CLI, API, and MCP operate under Remote's existing security and compliance posture, with the same rigour you already rely on.
Whether you embed Remote, build integrations, or add AI features, Remote offers the right interface for each workflow. Use the API for durable integrations. The CLI accelerates your teams' build and operations. MCP exposes Remote to AI agents.
With partners such as Personio and BambooHR, you deliver global employment for your customers through Remote. The CLI enables your team to test workflows in sandbox, debug problems, and run operational tasks more quickly, accelerating implementation and support.
Continue developing on Remote's public API for the durable integrations you've built. The CLI helps your team test endpoints, validate workflows, and debug issues more quickly.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether you're scripting, building an integration, or linking an AI tool, sign-in is simple and secure. There are no API keys to rotate and no secrets to store. Your Remote permissions apply across every surface.
For individual users signing in via browser (CLI, MCP).
For customer scripts and backend automation.
For partner integrations.
Sign in, follow the quickstart, and begin working in real time.