# ReMCP plugins ReMCP is designed to be installed from the plugin catalog of the AI host you already use. For normal users, the flow is: 1. Find **ReMCP** in the host's plugin browser. 2. Install it. 3. Sign in to ReMCP when the host asks you to connect. 4. Use the computers already paired to your ReMCP account. You do **not** need to paste an MCP server URL, edit a manifest, clone the repository, or configure a local path just to use the catalog plugin. Shareable install guides: - All integrations and current status: - [Complete tool reference](TOOLS.md): current production exposes 10 model-visible hosted definitions (8 device-facing façade tools + 2 account/fleet) covering all 83 granular runtime operations; explicitly re-enabling widgets adds 5 app-only UI helpers for 15 total definitions. - ChatGPT & Codex: - Claude Code: - Cursor Marketplace: The ReMCP-owned URLs are stable user-facing guides. They can later point to a more specific catalog card without changing the link you already shared. ## ChatGPT & Codex ChatGPT and Codex share OpenAI's unified public plugin directory. ### ChatGPT Open , search for **ReMCP**, and open the ReMCP plugin card when it is available for your account. Then: 1. Choose **Install plugin**. 2. Choose **Connect** if ReMCP authorization is requested. 3. Complete ReMCP OAuth. 4. Start a new chat and use **@ReMCP** or **+ → More** when those controls are available. If ReMCP is not visible yet, the listing or rollout is not available to that account. Do not paste an MCP endpoint or create a manual connection as a substitute for the catalog plugin. ### Codex In a supported Codex task view: 1. Open **Sources**. 2. Choose **Use plugins**. 3. Search for and select the installed **ReMCP** plugin. ChatGPT and Codex use the same public plugin directory, so there is no separate ReMCP package or MCP endpoint for users to configure. ## Claude Code ReMCP was submitted to Anthropic on **September 18, 2026** and currently shows **Submitted and pending review**. After approval, the preferred user flow is: 1. Open . 2. Filter for **Claude Code** if needed. 3. Search for **ReMCP**. 4. Choose **Install**. 5. Complete ReMCP authentication when Claude Code asks you to connect. Users do not clone the ReMCP repository or edit MCP configuration files. In Claude Desktop, the same catalog can also be reached from **+ → Plugins → Add plugin**. While the ReMCP listing is still under review, ordinary users do not need to add a marketplace, clone the repository, or paste an MCP endpoint. Developer and reviewer installation methods are kept in the technical Claude Code guide instead of the normal user flow. ## Cursor Cursor supports remote MCP servers without requiring a marketplace listing. To connect ReMCP: 1. Pair a computer to your ReMCP account. 2. Open Cursor's MCP settings and add an HTTP MCP server. 3. Use `https://remcp.site/mcp` as the endpoint (or set the same URL in `mcp.json`). 4. Complete the ReMCP OAuth authorization when prompted. 5. Ask Cursor Agent to use a paired computer. See [the Cursor setup guide](https://remcp.site/install/cursor) and [Cursor MCP documentation](https://cursor.com/docs/mcp). A packaged plugin artifact is not evidence that a marketplace has approved its listing. ## Gemini CLI ReMCP ships a native `gemini-extension.json` in the public repository and the repository carries the `gemini-cli-extension` topic used by Gemini CLI gallery discovery. Users can install directly from GitHub today: ```bash gemini extensions install https://github.com/antonbaider/remcp ``` Gemini CLI copies the extension locally. ReMCP's remote MCP entry uses OAuth discovery, so there is no static ReMCP token to paste into the extension. ## VS Code and other MCP-compatible clients Use a client's remote MCP settings to configure `https://remcp.site/mcp` when supported, then authorize through ReMCP OAuth. Follow the client documentation for the exact configuration fields. This is a generic MCP integration path, not a claim of marketplace approval. ## Kiro Powers ReMCP was submitted to the curated Kiro Powers registry on **September 19, 2026** and is pending review. Kiro uses the same Agent Plugins 1.0 package that ReMCP already publishes, so there is no separate Kiro-only MCP wrapper to maintain. Users can install ReMCP from GitHub before registry approval: 1. Open the **Powers** panel in Kiro. 2. Choose **Add Custom Power**. 3. Choose **Import power from GitHub**. 4. Enter `https://github.com/antonbaider/remcp`. 5. Install the power, complete ReMCP OAuth when prompted, and use a paired computer. After registry approval, users can discover ReMCP directly in . ## Cline ReMCP has been submitted to Cline's current MCP Marketplace source of truth: The open marketplace PR includes the hosted Streamable HTTP server, OAuth install metadata, and marketplace artwork. The direct CLI path was also smoke-tested during submission: ```bash cline mcp install remcp --transport http https://remcp.site/mcp --yes --json ``` After marketplace approval, users can find **ReMCP** in Cline's MCP Marketplace instead of entering the endpoint manually. ## Smithery, Glama, Awesome Remote MCP Servers, and the Official MCP Registry ReMCP is also published or indexed in the main MCP discovery layers: - **Smithery:** - **Glama:** - **Awesome Remote MCP Servers:** ReMCP is listed under Developer Tools after [PR #435](https://github.com/punkpeye/awesome-remote-mcp-servers/pull/435) was merged; the directory points to `https://remcp.site/mcp`. - **Official MCP Registry:** published as `io.github.getremcp/remcp`; GitHub resolves the project release URL `antonbaider/remcp` to the transferred repository owned by `getremcp`, so the Registry namespace remains valid while project-facing links use `antonbaider/remcp`. The former `io.github.antonbaider/remcp` Registry identity is legacy only. These are discovery/catalog surfaces rather than separate ReMCP accounts. They point users back to the same production service, OAuth boundary, and paired computers. See [DISTRIBUTION.md](DISTRIBUTION.md) for marketplace manifests, validation, and submission status. ## What the plugin carries for you Both host packages already contain the information needed to connect to ReMCP. The end-user install experience should therefore be described as: **Install from catalog → sign in to ReMCP → use paired computers.** The following details are implementation internals, not user setup steps: - MCP server endpoint; - host-specific manifest files; - OAuth metadata URLs; - review/submission JSON; - local development commands such as `--plugin-dir`. ## Developer and reviewer documentation Technical details are intentionally separated from the user install flow: - [OPENAI_PLUGIN.md](OPENAI_PLUGIN.md) — OpenAI packaging, MCP configuration, reviewer workflow, and submission artifacts. - [CLAUDE_CODE_PLUGIN.md](CLAUDE_CODE_PLUGIN.md) — Claude Code manifest, validation, local development, and Anthropic submission details. The two integrations still share the same ReMCP backend, OAuth account boundary, five operational skills, and paired-device trust model, while keeping host-specific packaging separate.