Introduction to Remote MCP

Use Remote.com MCP to connect an MCP-compatible AI client securely to your Remote employment data. Remote.com MCP is a hosted Model Context Protocol server that lets the AI answer questions, build artifacts, and run workflows over your live workforce data without exports, custom integrations, or hand-rolled API glue.

For example, ask your client "How many people do we have in Portugal?" It reads the question, fetches the answer from Remote through the MCP, and replies from your live data. The answer reflects your Remote data at the moment you ask, with nothing to export or refresh first.

If you've used Remote's REST API, think of MCP as the conversational layer on top of it: same data model, same permissions, but reached through natural language instead of HTTP calls.

One thing to keep in mind: the MCP is not an API you call yourself. Your AI client speaks the Model Context Protocol on your behalf, and every request runs under your Remote sign-in. If you need automated, server-to-server integration, use the REST API instead.

Prerequisites

Before you connect a client:

1. Sign in with a Remote account that can access the employment data you want to use.
2. Confirm your role in Remote has permission to access the relevant company-level or employee-level data.

Authentication

Remote.com MCP uses OAuth 2.0 Authorization Code with PKCE through the same browser sign-in you already use for Remote. You don't create API keys, store client secrets, or configure environment variables for MCP access.

The MCP client registers dynamically, sends you through Remote sign-in, and receives access based on your authenticated Remote account.

Required OAuth scopes

Remote.com MCP does not require you to request OAuth scopes manually.

What you can reach through it

Remote.com MCP exposes the domains that make up global employment at Remote:

• Read tools:
  • Employees and employment records
  • Contracts and contract amendments
  • Payroll runs, pay schedules, and deadlines
  • Time off, leave balances, and policies
  • Org structure and reporting lines
  • Legal entities and country-specific requirements
  • Timesheets, billing, and invoices
• Write tools (employee self-service, available today):
  • Submit time off requests
  • Update personal details, home address, emergency contact
  • Create and update career goals
  • Add and edit career journal notes

Clients discover the available tools automatically at connection time, so there's nothing to hardcode in your integration.

Who it's for

Remote.com MCP is available to employer users, such as company admins and managers, who can access company-level employment data, and to employees, such as EOR employees and contractors, who can access their own employment data. You don't choose a scope manually. The server reads access directly from your Remote account when you sign in, and the AI client only sees the tools your role is allowed to use.

How it's secured

• OAuth 2.0 with PKCE. The same browser sign-in you already use for Remote. No API keys to mint, no client secrets to store, no environment variables to configure.
• Role and RLS aware. Every request runs through Remote's existing permission model and Row-Level Security. The MCP layer can't see anything your account can't already see.
• Writes follow the same approval and audit flows as actions taken in the product. For example, a time off request created via MCP still goes to your manager for approval.

What it isn't

• It isn't a replacement for the Remote API when you're building a deterministic integration. For backend-to-backend automation, keep using the API directly.
• It isn't a chatbot Remote runs. The AI client is yours (Claude, Cursor, Codex, or anything else that speaks MCP). Remote provides the data layer.
• It isn't tied to one vendor. Any client that implements the MCP standard can connect.

Compatible clients

Remote.com MCP is tested against:

• Claude Desktop and claude.ai
• Claude Code
• Cursor

If you use an AI coding tool, the remote-for-ai plugin sets up this MCP server for you when installed, and adds skills for common workspace tasks. See Remote Agent Skills and the Build Integrations Quick Start.

Other MCP-compatible clients should work as long as they support OAuth 2.0 with Dynamic Client Registration over streamable HTTP.