remote.com
Remote provides employer-of-record, payroll, HR, and workforce-management services for globally distributed teams. Its platform lets companies and employees manage employment, payroll, benefits, time off, expenses, and related HR data.
Remote exposes one authenticated REST API at `https://gateway.remote.com` plus a hosted MCP server at `https://mcp.remote.com/mcp`; the API supports customer bearer tokens and several partner OAuth-based modes, and the MCP server uses OAuth login with a Remote account.
- Remote.com MCPdetected
- Remote APIdiscovered
In the Remote dashboard, go to Company → Company Settings → Integrations & APIs → Integrations, open the Remote API card, and click Generate API token. Only company admins or company owners can create or revoke the token. See Obtaining access token and Quick Start Guide for Customers.
Use your partner CLIENT_ID and CLIENT_SECRET to call POST https://gateway.remote.com/auth/oauth2/token (or sandbox https://gateway.remote-sandbox.com/auth/oauth2/token) with HTTP Basic auth and grant_type=client_credentials. Remote returns a bearer access_token valid for 3600 seconds. See Client Credentials Flow for Partners.
Register as a Remote API partner and obtain CLIENT_ID/CLIENT_SECRET, then send a company admin through Remote's OAuth authorization-code consent flow. After approval, exchange the returned code at POST https://gateway.remote.com/auth/oauth2/token (or sandbox) using HTTP Basic auth to receive a refresh_token, which you can later exchange for bearer access tokens. See Data sync for existing companies and Refresh Token Flow.
Vetted partners create a JWT with iss set to their CLIENT_ID, sub bound to the Remote user or employment being acted for, aud matching Remote's auth server, and sign it with their partner CLIENT_SECRET. Exchange it at POST /auth/oauth2/token with grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer to receive a bearer access token. See Authorization Method — OAuth Assertion.
$ claude mcp add --scope user --transport http remote-com-mcp https://mcp.remote.com/mcpAcquired by the CLI — running claude mcp add --scope user --transport http remote-com-mcp https://mcp.remote.com/mcp opens the auth flow and stores the credential.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing