Everything in Remote is reachable through the interface that best suits how you build.
The Remote API is engineered for production use. Build dependable integrations that synchronise 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 directly from the command line.
Connect ChatGPT, Claude, Cursor, or any MCP-compatible client to Remote. Query live workforce data, automate processes, and create AI assistants that understand your organisation.
The API, CLI and MCP are designed to interoperate.
Build 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 employ all three together.
Employees, contracts, payroll, expenses — sample data that lets you test API calls, CLI commands, and integrations without risking actual records.
Try connector workflows, troubleshoot integrations, validate commands. Every test runs on sandbox data.
Request access, sign in, 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—on realistic data without touching production.
You sign in. That is all. Authentication, permissions and compliance remain intact and apply automatically.
Sign in via your browser or use an API token—the same method you use for Remote. We do not require you to create API keys or retain secrets, and your credentials never reside in the tool you are integrating.
Whatever permissions you hold in Remote are preserved across the CLI/API/MCP. An employee can access employee data, an admin can access employer data, and nothing beyond those privileges.
The CLI/API/MCP present defined, structured endpoints rather than direct database access. Remote governs the responses, so you receive tidy data without bulk exports or unstructured dumps.
Remote returns only the data you request, and only to the specific tool or agent you authorised. Your workforce data is not used to train any AI provider’s models.
The CLI, API and MCP inherit Remote’s established security and compliance posture, with the same rigour you already rely on.
Whether you are embedding Remote, building connectors, or adding AI capabilities, Remote supplies the suitable interface for each workflow. The API supports durable integrations. The CLI lets your teams build and run faster. MCP exposes Remote to AI agents.
Like Personio, BambooHR, and others, you deliver global employment services to your customers via Remote. The CLI enables your team to test workflows in a sandbox, troubleshoot issues, and perform operational tasks more rapidly—accelerating implementation and support.
Continue developing on Remote's public API for the persistent integrations you have built. The CLI enables your team to test endpoints, validate workflows, and resolve issues more quickly.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether you are scripting, building an integration, or attaching an AI tool, authentication is straightforward and secure. No API keys to rotate. No secrets to store. Your Remote permissions apply across every interface.
For individual users signing in via browser (CLI, MCP).
For direct customer scripts and backend automation.
For partner integrations.
Sign in, follow the quickstart, and begin working in real time.