Remote.com

Name: Remote.com MCP Server
Availability: InStock
Author: Remote.com

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Productivity51 tools

Query global employment, payroll, time off and org structure. 51 tools, and the first OAuth scopes here split by persona: admin, employer, employee.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Remote.com via MCP

https://mcp.remote.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Remote.com once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Remote.com Tools & Capabilities (51)

get_personal_information

get_home_address

get_emergency_contact

get_default_bank_account

list_bank_accounts

get_employee_personal_info

get_payroll_calendar

list_employee_payslip_files

get_payslip_breakdown

list_employee_payroll_outputs

get_employee_time_balance

get_timeoff_leave_policies_summary

list_employee_timeoffs

get_employee_timeoff

list_paid_timeoff_days

list_employee_holidays

get_work_calendar

list_employee_expenses

get_employee_expense_stats

list_contractor_invoices

get_contractor_invoice

list_employee_career_goals

list_career_feedback

list_employee_documents

list_employee_notifications

get_employee_org_chart

get_company

get_company_stats

list_company_employees

list_company_employments

list_company_admins

list_company_departments

list_team_members

list_company_public_holidays

get_employee_pay_details_aggregates

list_employer_payroll_history

list_payroll_inputs

get_billing_dashboard

list_billing_documents

get_timeoff_dashboard

get_timeoff_team_absence_dashboard

list_timeoffs

list_expenses

get_expense_dashboard

get_headcount_over_time_report

get_workforce_breakdown

get_turnover_and_retention_report

list_employer_legal_entities

list_jobs

list_compensation_cycles

list_employer_performance_cycles

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

This connector writes. Remote documents write tools for submitting and approving time off, creating and updating expenses, updating personal details, home address and emergency contact, managing performance reviews, configuring workflows and creating data exports. Anthropic's 51 names contain none of them, so the directory listing understates the surface.
It does not move money. Remote states the connector cannot move money, or start payments, payouts or payroll runs, and cannot change salary or contract terms. This is a vendor statement, and it is the load-bearing difference from a payroll connector that can submit a run.
mcp:remote_admin:lite is undocumented. Remote publishes no definition of what the lite admin scope restricts, at any of the four sources we searched. If a consent screen requests it, its reach is undetermined.
The role gate is narrower than the docs suggest. Remote's MCP documentation describes manager workflows and its example prompts include a manager section, but Remote's role matrix — updated 2026-08-12 — marks Remote MCP access as available to company owners and super admins only, and unavailable to people managers, hiring managers, onboarding managers and company viewers. Those two Remote sources disagree. Verify against your own account.
It reads bank accounts, home addresses and emergency contacts of employees and contractors. get_default_bank_account, list_bank_accounts, get_home_address and get_emergency_contact are in the published list.
The transcript is the exposure Remote flags, not the server. Remote warns that your questions and its answers may be retained in the AI client's conversation history depending on that client's settings, and states it has no control over how the client processes or stores what it receives.
Tool parameters and safety annotations were not readable. The endpoint returned HTTP 401 to an anonymous initialize on 2026-08-18 and HTTP 406 to a GET, so names came from the directory snapshot and meanings from Remote's documentation. No tool was called.
The published lists do not agree with each other. The directory names 51 tools; Remote's own plugin skills name 42 tool-shaped identifiers with only 9 in common; and one of those skills contradicts itself about whether two cancellation tools are exposed at all. Expect the live surface to differ from every published list.
It is not a backend integration. Remote states the MCP is not an API you call yourself, that every request runs under your interactive sign-in, and that server-to-server automation should use the REST API instead. Its General Ledger report flow is explicitly interactive — an admin drives it — with an unattended API path described as "coming soon".
No rate limits are published for the MCP server. Remote publishes a rate limit policy for its REST API; we found none stated for MCP. Remote's own reporting skill notes large tool responses can be truncated, and recommends field projection and paging.

Frequently asked questions

Remote states the connector applies the same controls that already protect the account. Sign-in is OAuth in your own browser, so the password never reaches the AI client; every request runs through Remote's roles, permissions and Row-Level Security; traffic is encrypted with TLS. Remote notes its platform is ISO 27001 certified and that data reaching your client falls under that client's policy.

Remote reuses the roles you already have. Three layers apply: your Remote role, role-based permissions that decide which tools are exposed at all, and Row-Level Security that limits what each tool returns. Remote's summary is that a manager sees only direct reports and an employee sees only themselves. Nothing is granted that signing in directly would not grant.

You need an active Remote account and an MCP-compatible client. Remote tests Claude Desktop, claude.ai, Claude Code and Cursor. Nothing is installed on the Remote side. Remote's role matrix, however, marks Remote MCP access as available to company owners and super admins only, and unavailable to people managers, hiring managers, onboarding managers and company viewers.

The same data you see when you sign in to Remote, and nothing beyond it. Remote adds a warning worth heeding: anything typed into the AI client, including parts of your questions and Remote's answers, may be stored in that client's conversation history depending on its settings. Remote advises against sharing sensitive information you do not want retained outside Remote.

Only what they could already see by signing in to Remote directly. Remote states a manager can ask about their direct reports' employment details and time off, plus org structure and reporting lines, where Remote already permits it. Connecting an AI client does not change the permissions that protect your record from other people.

Remote tests Claude Desktop, claude.ai, Claude Code and Cursor. Its documentation adds that any other client should work provided it supports OAuth 2.0 with Dynamic Client Registration over streamable HTTP. For coding tools, Remote publishes a remote-for-ai plugin that configures the connection for Claude Code, Cursor, Codex and Gemini CLI.

Remove the connection in your AI client's own settings. Remote states users can disconnect at any time, and that access is revoked automatically when a Remote account is deprovisioned — so offboarding someone in Remote also cuts off whatever AI client they had connected. There is no separate token to revoke inside Remote.