01
AGENTS
Multi-step agents
Run autonomous workflows on Remote data. The agent runs, the work gets done.
Connect any AI tool to
MCP-compatible tools you already use
Claude
ChatGPT
Cursor
Claude Code
Copilot
Remote ran the foundation
WHAT IT UNLOCKS
01 / 06
Chat with your workforce data
Everything you manage in Remote is now accessible to any AI tool your team uses. Instead of exporting spreadsheets, building reports, or stitching together VLOOKUPs, HR and Payroll teams can now query live workforce data directly from chat.
BUILD WITH IT
02 / 06
Or build something
MCP turns Remote into a live data layer any AI agent or app can build on. Build dashboards, audits, multi-step workflows, and entirely new tools — all running on real workforce data.
02
ORCHESTRATE
Cross-system orchestration
Combine Remote data with Salesforce, Notion, Google Drive, or anything else your AI tool can reach.
AS SECURE AS REMOTE ITSELF
03 / 06
Connecting via MCP is as secure
Connecting
via MCP
is as
secure
You sign in. That’s it. The authentication, the permissions, and the compliance posture all carry over.
⌐sign-in oauth2
OAuth 2.0
Sign in through your browser, the same way you log into Remote. We don't ask you to generate API keys or store secrets, and your credentials never touch the AI tool you're using.
◈inherited RBAC
Role-aware
Whatever permissions you have in Remote, you have through MCP. An employer admin sees employer data; an employee sees their own, and nothing more.
⊟curated endpoints
Governed tools
MCP exposes specific, structured endpoints, not raw database access. Remote controls what's returned, so AI tools can't pull bulk exports or unstructured data dumps.
◎privacy data use
Your data stays your data
Remote sends only what you ask for, and only to the AI tool you've signed into. Your workforce data isn't used to train any AI provider's models.
◉ISO 27001 certified
SOC 2 Type II compliant
MCP runs on Remote’s existing security and compliance posture, with the same rigor you already trust.
Three ways in
04 / 06
Connect in
Open your client, paste a URL, sign in. That’s it. Your assistant now has access to whatever Remote tools your role allows. No API tokens, no JSON config, no admin tickets.
01
Pick your tool.
These clients work today or ship soon—desktop apps, IDEs, the CLI, or anything that speaks MCP.
Claude
Claude Desktop
Claude Code
Cursor
ChatGPT (soon)
Codex (soon)
Claude Desktop
Claude Code
Cursor
ChatGPT (soon)
Codex (soon)
02
Add the connector.
Paste one URL, into your tool’s connector or MCP config. Walkthroughs for each tool below.
03
Sign in, then ask.
Two quick logins: Claude, then Remote. Your role determines which tools become available. After that, just type.
See here how to set up the MCP connector for each tool
Connect from claude.ai
The browser app — quickest path, no install.
- Open claude.ai. Click your avatar (bottom-left) → Settings → Connectors.
- Scroll to Add custom connector.
- Paste these two values:
Name
URL
- Click Add, then Connect. Sign in with your Remote account — you’ll see Okta first, then the Remote login.
- Open a new chat. Ask: “show me my pending PTO requests”. Remote tools appear in the toolbox automatically.
Heads up: the tools you see depend on your Remote role. Manager profiles unlock more (e.g. approving PTO) than individual profiles.
Connect from Claude Desktop
The macOS / Windows app. Connectors sync with claude.ai — set it up once, both clients get it.
- Open Claude Desktop. Click your avatar (top-right) → Settings → Connectors.
- Click Add custom connector.
- Paste the same two values:
Name
URL
- Click Add and authenticate via Okta + Remote. No app restart needed.
- Start a chat — Remote tools are immediately available.
Already set up on claude.ai? You’re done — Claude Desktop will inherit the connector automatically.
Connect from Claude Code (CLI)
For the terminal-native crowd. One command, OAuth handled in your browser.
- In your terminal:
- The first time you call a Remote tool, Claude Code opens your browser for the OAuth handshake (Okta + Remote).
- Try it:
claude, then ask “list my last three payslips”.
Verify: run
claude mcp list — you should see remote with status connected.
Connect from Cursor
HTTP MCP via a config file. Same shape works in Continue, Zed, Windsurf, and most other IDEs.
- Create or edit
.cursor/mcp.jsonin your project root (or~/.cursor/mcp.jsonglobally) with:
- Open Cursor’s Settings → MCP panel and click Reload MCP servers (or quit and relaunch Cursor).
- Authenticate via the browser when Cursor prompts you.
- Open Composer or chat — Remote tools are now in the toolbox.
Same JSON shape works in Continue (
~/.continue/config.json), Zed (settings.json), and Windsurf — paste it into their respective MCP block.
Generic MCP configuration
For any client that speaks the Model Context Protocol — current or future.
- Endpoint:
https://mcp.remote.com/mcp - Protocol: MCP
2025-06-18or current spec.
FOR PARTNERS
05 / 06
If your product runs on Remote (through embedded employment, integrations, or custom APIs) MCP gives your customers a new AI-native way to interact with the workforce data your product manages. Your existing API integrations keep doing what they do. MCP layers on top.
01
EMBEDDED
Embedded partners
Workday, Gusto, BambooHR, Personio, and others already provide global employment for their customers through Remote. MCP extends that to AI tools, without anything to rebuild on your end.
02
INTEGRATION
Integration partners
Continue using Remote's public API for the durable read/write integrations you've built. MCP is the AI-native complement.
FOR DEVELOPERS
06 / 06
No keys, no secrets,
Remote MCP uses OAuth 2.0 with PKCE and dynamic client registration. There's nothing to provision, store, or rotate. Your client registers itself, the user signs in through their browser, and access is scoped to their existing Remote role automatically.
Ready to connect?
Sign in, follow the quickstart, and start working in real time.