Everything in Remote is accessible through the interface that best fits how you build.
The Remote API is designed 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 command line.
Connect ChatGPT, Claude, Cursor, or any MCP-compatible client to Remote. Query live workforce data, automate workflows, and create AI assistants that understand your organization.
The API, CLI, and MCP are built to work together.
Use the API to create production-grade integrations, rely on the CLI for operational tasks, and attach MCP when AI must interact with 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 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—API calls, CLI workflows, and integrations—on realistic data without touching production.
You sign in. That's all. Authentication, permissions, and the compliance posture all carry over.
Sign in via your browser or use an API token—the same method you use to log into Remote. We don't require generating API keys or storing secrets, and your credentials never touch the tool you're using.
Any permissions assigned to you in Remote apply in the CLI, API, and MCP. An employee can view employee data, an admin can access employer data, and no other data.
The CLI, API, and MCP provide defined, structured endpoints rather than raw database access. Remote governs the responses, so you receive clean data without bulk exports or unstructured dumps.
Remote transmits only the data you request, and only to the specific 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 rigor you trust.
Whether you're embedding Remote, creating integrations, or adding AI capabilities, Remote supplies the appropriate interface for each workflow. The API enables durable integrations. The CLI helps your teams develop and operate more quickly. MCP exposes Remote 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 sandbox, debug issues, and run operational tasks faster—accelerating implementation and support.
Keep building on Remote's public API for the durable integrations you've already created. 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, developing an integration, or connecting an AI tool, authentication is simple and secure. No API keys to rotate. No secrets to store. Your Remote permissions apply across every surface.
For individual users logging 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.