Remote MCP vs. Remote API vs. Remote Agent: which one do I use?

Remote offers multiple ways to connect to your employment data. Each one is built for a different kind of work.

Remote MCP

Remote MCP connects any MCP-compatible AI client to your Remote account. The AI discovers the tools it needs and runs them for you when you ask a question in plain language.

Use Remote MCP when:

• You want an AI assistant to query Remote on your behalf.
• The work is exploratory, ad-hoc, or conversational.
• You do not need a stable, versioned integration.

Remote API

The Remote API is the stable, versioned set of endpoints documented at developer.remote.com. It is designed for code that needs to keep working the same way every time it runs.

Use the Remote API when:

• You are building a long-lived integration or automation.
• You need stable, versioned behavior.
• A human or a script will call it directly.

Remote Agent

Remote Agent is an AI assistant inside the Remote platform. It works within Remote's own interface and can support in-platform workflows.

Use Remote Agent when:

• You want AI help or insights while staying inside Remote.
• The task lives in Remote's UI rather than in an external AI client.

Quick rule of thumb

• An external AI doing the work for you, on demand: Remote MCP.
• Stable code calling Remote: Remote API.
• AI help inside Remote itself: Remote Agent.

Data handling: Remote MCP routes data to your chosen third-party AI client. Remote Agent and the Remote API keep data within Remote's own infrastructure.