6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Query global employment, payroll, time off and org structure.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Remote.com MCP server connects a Remote employer-of-record account to Claude, Cursor and any MCP-compatible agent. It exposes 51 tools covering employment records, payroll, payslips, time off, expenses, org structure and workforce reporting. Sign-in is OAuth, and the server advertises seven scopes split by persona — admin, employer and employee — which no other connector here does.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.get_default_bank_account, list_bank_accounts, get_home_address and get_emergency_contact are in the published list.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.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.
.md appended, updatedAt 2026-07-15). developer.remote.com/robots.txt allows this path, names its own llms.txt, and carries no Content-Signal line. · retrieved 2026-08-18updatedAt 2026-07-17) · retrieved 2026-08-18remote-for-ai plugin and its operate-vs-build split (retrieved 2026-08-18) · retrieved 2026-08-18lite appears nowhere on the developer site (475 lines, retrieved 2026-08-18) · retrieved 2026-08-18remoteoss/remote-for-ai plugin skills, for the named write tools, the confirm-before-writing rule, the PII handling rules and the self-contradiction about cancellation tools (retrieved 2026-08-18) · retrieved 2026-08-18updated_at 2026-07-01, retrieved 2026-08-18) · retrieved 2026-07-01updated_at 2026-06-17) · retrieved 2026-06-17updated_at 2026-06-17) · retrieved 2026-06-17updated_at 2026-06-17) · retrieved 2026-06-17updated_at 2026-08-12). Articles were read through Zendesk's public Help Center API; support.remote.com/robots.txt permits /hc/*/articles/ and carries no Content-Signal line. · retrieved 2026-08-12https://mcp.remote.com/mcp — initialize returned HTTP 401 with WWW-Authenticate: Bearer resource_metadata="https://mcp.remote.com/.well-known/oauth-protected-resource/mcp" (2026-08-18). A GET on the same host returned HTTP 406, so no public tool catalogue is served. No tool was called. · retrieved 2026-08-18authorization_servers: ["https://api.employ.remote.com"] and the seven persona scopes. The sandbox host publishes the identical seven. · retrieved 2026-08-18S256 only, authorization_code and refresh_token grants, and a registration_endpoint. It publishes no scopes_supported field, so the descriptor is the only scope source. The same document is served from mcp.remote.com. · retrieved 2026-08-18Connect Remote.com once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.