---
title: "How do I add a remote MCP server to Cline?"
description: "To add a remote MCP server to Cline, open MCP Servers, use the Remote Servers tab, enter a name and URL, pick Streamable HTTP and click Add Server."
updated: 2026-10-21
---

To add a remote MCP server to Cline, click the **MCP Servers** icon in the Cline panel, open the **Remote Servers** tab, enter a server name and the full endpoint URL, choose **Streamable HTTP** as the transport type, and click **Add Server**. In the Cline CLI, run `cline mcp` and add the server in its wizard instead.

For Wireflow, the server URL is `https://www.wireflow.ai/api/mcp`, and you sign in with your Wireflow account instead of pasting an API key. Cline can then build and run workflows on your credits, read the results, and generate and edit images, video and audio across 100+ models.

Setting up a different agent? Start from the guide to [connecting your AI agent](/docs/use-wireflow-from-your-agent), which covers Claude, Cursor, Codex and ChatGPT, or follow the [GitHub Copilot setup](/docs/agents/github-copilot) for Copilot in VS Code.

## Where do I put the MCP server URL in Cline?

Put it in the **Server URL** field of the **Remote Servers** tab, which adds a hosted endpoint without editing any JSON. Filled in for Wireflow, the steps are:

1. In the Cline panel, click the **MCP Servers** icon, the stacked server icon in the top toolbar.
2. Open the **Remote Servers** tab.
3. In **Server Name**, enter `wireflow`. Any unique label works.
4. In **Server URL**, enter the full endpoint URL: `https://www.wireflow.ai/api/mcp`.
5. Under **Transport Type**, choose **Streamable HTTP**. Cline's docs mark it as recommended, with **SSE (Legacy)** as the other choice, and Wireflow's server is a Streamable HTTP endpoint.
6. Click **Add Server**.

Then sign in with your Wireflow account, as the OAuth section below explains.

## How do I configure a Streamable HTTP MCP server in Cline's settings file?

Add an entry under `mcpServers` in Cline's MCP settings JSON, with `"type": "streamableHttp"` and the server's `url`. Where you find that file depends on how you run Cline:

- **IDE extensions:** click the **MCP Servers** icon, open the **Configure** tab, and click **Configure MCP Servers** near the bottom. This opens the MCP settings JSON the extension uses.
- **Cline CLI:** edit `~/.cline/data/settings/cline_mcp_settings.json`, or the file the `CLINE_MCP_SETTINGS_PATH` environment variable points to.

For Wireflow, the entry looks like this:

```json
{
  "mcpServers": {
    "wireflow": {
      "type": "streamableHttp",
      "url": "https://www.wireflow.ai/api/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
```

Keep the `type` line. Cline's docs say that leaving it out defaults to the legacy `sse` transport, so set `streamableHttp` explicitly.

Cline's remote example also has a `headers` block with a bearer token. Leave it out for Wireflow: you sign in with OAuth, and there is no client ID or API key to paste. The Cline CLI takes the same server definitions as the extension.

## How do I add a remote MCP server with the Cline CLI?

Run `cline mcp add` with a name and the server URL, or run `cline mcp` and use its **Add server** action. For Wireflow, the one-line version is:

```bash
cline mcp add wireflow https://www.wireflow.ai/api/mcp --transport http --yes
```

This follows Cline's own example for a remote server, without the `--header` option, because Wireflow uses no API key. Without `--yes`, `cline mcp add` opens the add wizard with those fields filled in.

If you start from the `cline mcp` menu instead, the CLI prompts for the server name, the transport type, and the URL and headers for a remote server. To list your servers without the wizard, run `cline config mcp` or `cline config mcp --json`. To remove the server later, run `cline mcp remove wireflow`.

## How do I sign in to a remote MCP server with OAuth in Cline?

In the Cline CLI, run `cline mcp` and choose **Authorize OAuth**, which runs or reruns browser authorization for a remote server. Wireflow's connector signs your agent in with OAuth instead of an API key.

Wireflow's [MCP connector page](/docs/mcp) says the client walks you through Wireflow's OAuth sign-in and a consent screen. Sign in with your Wireflow account, then approve the consent screen, which lists exactly the permissions the client asked for. Wireflow uses the OAuth 2.1 authorization code flow with PKCE, and clients self-register with no pre-shared credentials.

On Wireflow's side, a client that asks for nothing in particular gets the read and run scopes. The run scope, `workflows:execute`, runs your workflows on your behalf and spends credits. Opt-in permissions, such as `workflows:write` and `social:publish`, are withheld unless the client names them. You can revoke access at any time from your Wireflow settings.

## How do I test that Cline can use the Wireflow tools?

Check that the Wireflow tools appear in Cline, then test one tool call, which is how Cline's MCP quick start ends. In the CLI, the **List servers** action in `cline mcp` shows each configured server and whether it is enabled.

For the tool call, paste this prompt into Cline. It only reads your account, so it spends no credits:

```text
Use Wireflow. Tell me which Wireflow account you are connected as and what my credit balance is.
```

Two Wireflow tools answer it: `whoami` confirms which account the connection acts as, and `get_credit_balance` checks your credit balance and plan. Review each tool call before you approve it, as Cline's security basics advise.

When that works, try a first image. This prompt asks Cline to name the model and its credit cost, then wait for your yes:

```text
Use Wireflow to make a photo of a ceramic coffee mug on a wooden table in soft morning light. Pick an image model, tell me which one and its credit cost, and wait for my yes before you run it.
```

Wireflow's `list_models` tool lists the available image, video and audio models with real prices, and `run_workflow` runs a workflow and consumes credits on the connected account. Keep tools that spend credits, such as `run_workflow`, out of `autoApprove`: Cline's docs say to limit it to safe tools. For plans and credits, see the [pricing page](https://www.wireflow.ai/pricing).

To start runs from your own scripts and servers instead of an agent, use an API key, which starts with `sk-`, and [run a workflow over the API](/docs/api/run).

## Why won't my remote MCP server connect in Cline?

Start with the URL and the transport: when a server won't connect, Cline's docs say to verify the URL, and Wireflow's endpoint is `https://www.wireflow.ai/api/mcp` over Streamable HTTP. Then match what you see:

| What you see | What to check |
| --- | --- |
| The server won't connect | The URL is exactly `https://www.wireflow.ai/api/mcp` and the transport is **Streamable HTTP**. In the settings JSON, a missing `type` falls back to the legacy `sse` transport |
| Auth errors | Cline's fix is to re-check API keys, tokens and required headers. Wireflow needs no API key, so rerun the sign-in with **Authorize OAuth** in `cline mcp` |
| The Wireflow tools are missing | The server started and is enabled, and you finished the Wireflow sign-in. **Enable/disable server** in `cline mcp` toggles a server without deleting it |
| Timeout errors | Increase the MCP timeout, then test again |

If Cline still [can't find the Wireflow tools](/docs/troubleshooting), see Wireflow's troubleshooting page.

Last updated: 2026-10-21

---

Documentation index: fetch https://www.wireflow.ai/llms.txt for the full list of Wireflow docs.