Everything in Remote is available through the interface that suits how you build.
The Remote API is designed for production. Build reliable integrations that sync workforce data, automate business processes, and power applications over time.
The Remote CLI speeds up everyday tasks. Manage your workforce, automate recurring jobs, and access Remote without leaving your terminal.
Connect 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 operate together.
Use the API for production integrations, rely on the CLI for operational tasks, and enable MCP when AI must access your workforce data. Most teams use 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, debug integrations, and validate commands. All tests run on sandbox data.
Request access, sign in, and begin testing.
$ remote sandbox --init
Use a sandbox prepopulated with employees, contracts, payroll, and expenses. Test your connectors—API calls, CLI workflows, and integrations—on realistic data without touching production.
Sign in once, and that's enough. Your authentication, permissions, and compliance posture carry across interfaces.
Sign in via your browser or use an API token, just as you do for Remote. You won't need to create API keys or store secrets, and your credentials never leave the tool you're signed into.
Your permissions in Remote apply to the CLI/API/MCP. An employee can view employee data, an admin can access employer data, and no excess access is granted.
The CLI/API/MCP present defined, structured endpoints rather than direct database access. Remote governs responses, giving you tidy data without bulk exports or unstructured dumps.
Remote only returns the data you request, and only to the tool or agent you've authenticated. 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 trust.
If you're embedding Remote, building integrations, or adding AI features, Remote supplies the right interfaces for each workflow. The API supports durable integrations. The CLI helps your teams develop and operate faster. MCP makes Remote accessible to AI agents.
Like Personio, BambooHR, and others, you deliver global employment for your customers via Remote. The CLI lets your team test workflows in a sandbox, debug issues, and perform operational tasks faster, accelerating implementation and support.
Keep building on Remote's public API for the durable integrations you have developed. The CLI lets your team test endpoints, validate workflows, and troubleshoot issues more quickly.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether you are writing a script, building an integration, or linking an AI tool, auth is simple and secure. No API keys to rotate. No secrets to store. Your permissions in Remote apply across every surface.
For individual users signing in through a browser (CLI, MCP).
For direct customer scripts and backend automation.
For partner integrations.
Sign in, follow the quickstart, and begin working in real time.