Remote MCP Server
Connect any AI agent to Remote's global payroll, EOR, and workforce data over MCP.
Updated
What is Remote MCP?
The Remote MCP server is a Model Context Protocol server that gives any MCP-compatible AI agent a live, secure connection to your Remote global-employment data — payroll, contracts, compliance records, and org structure — without API keys, spreadsheet exports, or custom integrations.
Remote is a global employment infrastructure platform covering Employer of Record (EOR) hiring, contractor management, global payroll, benefits, and worldwide payments. The MCP server, hosted by Remote at https://mcp.remote.com/mcp, lets tools like Claude, Claude Code, and Cursor query live workforce data and run multi-step workflows directly from chat instead of building reports or stitching together exports.
Connections authenticate over OAuth — you sign in through your browser via your existing Remote login, and the agent only sees data your Remote role and permissions already allow. Because it's a remote, vendor-hosted server, there's nothing to install or self-host: you point your MCP client at the URL and complete the OAuth flow.
Connect the Remote MCP server
Claude Code
- 1
Add the Remote MCP server
Run: claude mcp add --transport http --scope user remote https://mcp.remote.com/mcp
- 2
Authenticate via OAuth
Run /mcp in Claude Code and complete the browser OAuth sign-in with your Remote account. Claude Code flags the server for auth when it returns 401/403.
- 3
Verify the connection
Run /mcp again to confirm the 'remote' server is connected, then ask the agent to query your workforce data.
Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP (or edit ~/.cursor/mcp.json) to add a new server.
- 2
Add the Remote server
Add an entry for the streamable-HTTP URL https://mcp.remote.com/mcp (name it 'remote'), then reload Cursor.
- 3
Sign in with OAuth
When prompted, complete the browser OAuth flow with your Remote login. The Remote tools then appear to the agent in Cursor.
Security & permissions
Authentication uses OAuth 2.0 (with PKCE and dynamic client registration) — you sign in through your browser via your existing Remote login rather than managing API keys or static secrets. The agent's access is scoped to your Remote role and permissions, so it can only read or act on the workforce data (payroll, contracts, compliance, org structure) you're already authorized to see. Because the server is hosted by Remote, your data is queried live against Remote's platform; no exports or copies are required to connect.
Using Remote MCP with Gamut
In Gamut, you add Remote as a connected tool and let an agent call it inside an automated, event- or schedule-triggered workflow — for example, a weekly run that queries headcount, contract-renewal dates, or PTO balances and routes the result into a Slack summary or a downstream system. Gamut manages the OAuth connection to https://mcp.remote.com/mcp, so the agent operates within your existing Remote permissions and you don't hand-wire credentials per run. The agent can read live workforce data and combine it with other connected tools; it should not be assumed to perform payroll-changing actions beyond what your Remote role permits.
Frequently asked questions
What is the Remote MCP server?
It's a Model Context Protocol server hosted by Remote that gives AI agents a live, secure connection to your Remote global-employment data — payroll, contracts, compliance, and org structure — so tools like Claude and Cursor can query that data without API keys or exports.
Is the Remote MCP server free?
Remote does not publish a separate price for the MCP server; it's offered as part of the Remote platform, and access is gated by your existing Remote account and role permissions. Check Remote's documentation or your account team for current terms.
How do I connect Remote MCP to Claude Code or Cursor?
In Claude Code, run 'claude mcp add --transport http --scope user remote https://mcp.remote.com/mcp', then run /mcp and complete the browser OAuth sign-in. In Cursor, add the same URL (https://mcp.remote.com/mcp) to your MCP settings / ~/.cursor/mcp.json, reload, and authenticate when prompted.
Is the Remote MCP server hosted or self-hosted?
It's hosted by Remote at https://mcp.remote.com/mcp — there's nothing to install or self-host. You point your MCP client at the URL and authenticate over OAuth using your Remote login.