Build Integrations Quick Start

Install the remote-for-ai plugin in your AI coding assistant and start building against the Remote API with skills that load automatically.

📘

Skills are optional

If you only need API context, skip the install and point your assistant at https://developer.remote.com/llms.txt. The steps below add the skills on top for a guided, validated workflow.

Prerequisites

• A Remote account.
• One of Claude Code, Cursor, Codex, or Gemini CLI installed.

Install

Claude Code

/plugin marketplace add remoteoss/remote-for-ai
/plugin install remote@remote-plugin-marketplace

Restart Claude Code.

Cursor

Search for Remote in Cursor Settings > Plugins and install. For local development:

git clone https://github.com/remoteoss/remote-for-ai
ln -s "$PWD/remote-for-ai" ~/.cursor/plugins/local/remote

Codex

codex plugin marketplace add remoteoss/remote-for-ai

Then run /plugins inside Codex, select Remote, and install.

Gemini CLI

gemini extensions install https://github.com/remoteoss/remote-for-ai

This bridges the HTTP MCP endpoint via npx mcp-remote@latest, since Gemini CLI currently supports only stdio MCP servers.

From source (any client)

git clone https://github.com/remoteoss/remote-for-ai

# Claude Code
claude --plugin-dir ./remote-for-ai

# Cursor
ln -s "$PWD/remote-for-ai" ~/.cursor/plugins/local/remote

# Codex
codex --plugin-dir ./remote-for-ai

# Gemini CLI
gemini extensions install ./remote-for-ai

Verify

In Claude Code:

/help    # lists all eight /remote:* skills
/mcp     # shows the `remote` MCP server

/help lists all eight skills the plugin ships, including the operator skills for running your workspace. See Remote Agent Skills for what each one does. The remote MCP server is the connection those operator skills use; the Remote MCP Quick Start covers it.

Authenticate

There are two separate credentials involved. Don't mix them up:

Your integration's API access (what the skills help you build). The code you write calls the Remote API with its own credentials: an API token for customers (generated in Remote under Company Settings > Integrations & APIs, requires admin or owner permissions) or an OAuth 2.0 app for partners. The remote-api-auth skill walks your assistant through choosing the right flow, acquiring tokens, and handling refresh. Use sandbox credentials while developing, never production. To get a seeded sandbox company and a ra_test_ token, follow the Sandbox Quickstart.

The plugin's in-editor MCP connection. The plugin also configures the Remote MCP server. The first time your assistant invokes a Remote MCP tool directly, it prompts you to sign in to Remote via OAuth in your browser. This connection has no API keys to copy. It authenticates you in the editor, not the integration you're building. For what you can do over that connection, see the Remote MCP Quick Start.

Try it

Ask your assistant a build-focused question, for example:

"Using the Remote API in sandbox, list our company's employments and show me how to page through them."

The remote-api-integration skill loads, reads Remote's machine-readable index at llms.txt to find the right endpoint and confirm its contract, then generates the call:

curl -s \
  -H "Authorization: Bearer $REMOTE_SANDBOX_TOKEN" \
  "https://gateway.remote-sandbox.com/v1/employments?page_size=20&page=1"

It then walks you through paging with current_page and total_pages. The right skill always loads automatically based on what you ask.