Everything in Remote is accessible via the interface that best fits how you build.
The Remote API is built for production. Build reliable integrations that sync workforce data, automate business processes, and power applications for the long term.
The Remote CLI makes everyday tasks faster. Manage your workforce, automate recurring jobs, and access Remote from the command line.
Connect ChatGPT, Claude, Cursor, or any MCP-compatible client to Remote. Query live workforce data, automate workflows, and build AI assistants that understand your organization.
The API, CLI, and MCP are designed to work together.
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 use a combination of all three.
Employees, contracts, payroll, and 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. Every test runs on sandbox data.
Request access, sign in, start testing.
$ remote sandbox --init
Access a sandbox that is 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's it. Authentication, permissions, and the compliance posture carry over.
Sign in via your browser or use an API token, just as you log into Remote. You don't need to generate API keys or store secrets, and your credentials never touch the tool you use.
Whatever 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 specific, structured endpoints instead of raw database access. Remote governs the responses, so you receive clean data without bulk exports or unstructured dumps.
Remote returns only the data you request, and solely to the tool or agent you signed into. 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 already rely on.
Whether you're embedding Remote, building integrations, or adding AI capabilities, Remote supplies the right interface for each workflow. The API enables durable integrations. The CLI helps teams build and operate more quickly. MCP exposes Remote to AI agents.
Like Personio, BambooHR, and others, you deliver global employment for your customers through Remote. The CLI helps your team test workflows in sandbox, debug issues, and run operational tasks faster, accelerating implementation and support.
Continue building on Remote's public API for the durable integrations you've 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 writing a script, building an integration, or connecting an AI tool, authentication is straightforward and secure. No API keys to rotate. No secrets to store. Your permissions in Remote 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.