Wireflow/Docs

Why won't my AI agent connect to the Wireflow MCP server?

Your AI agent won't connect to the Wireflow MCP server when the URL or transport is wrong, the sign-in is unfinished or the server is turned off.

Last updated View as Markdown

Your AI agent won't connect to the Wireflow MCP server when its entry has the wrong URL or transport, the Wireflow sign-in isn't finished, or the server is turned off in the client. Each section below starts from one error or status text that the client's own docs name, then gives the cause, the fix and a check.

On the Wireflow side, every client does the same thing. It points at the Streamable HTTP endpoint https://www.wireflow.ai/api/mcp, then walks you through Wireflow's OAuth sign-in and a consent screen. There is no API key and no client ID to add, because clients register themselves. Every permission and tool is listed on the MCP connector page.

Each Check ends with this prompt. Your agent should call whoami, which confirms which Wireflow account the connection acts as and spends no credits:

Use Wireflow and tell me which Wireflow account you are connected as.

Haven't added Wireflow yet? Start with How do I connect my AI agent to image and video generation tools? For agents not covered below, go to their own fix sections:

For API, upload and webhook errors, see Troubleshooting.

Why does Claude Code say "Failed to connect" for the Wireflow MCP server?

✘ Failed to connect means Claude Code couldn't connect to the server, and claude mcp get wireflow shows why on its Issue: line.

Cause: The Issue: line holds the HTTP status or error code, plus any error text the server returned. Claude Code doesn't retry an authentication or not-found error, because it needs a change to your configuration. It retries a transient error on the first connection, such as a 5xx response, a refused connection or a timeout, up to three times.

Fix:

  1. Run claude mcp get wireflow and check that the URL is exactly https://www.wireflow.ai/api/mcp. The Issue: detail needs Claude Code v2.1.219 or later.
  2. If the URL is wrong, remove the server and add it again:
claude mcp remove wireflow
claude mcp add --transport http wireflow https://www.wireflow.ai/api/mcp
  1. Run /mcp and sign in to Wireflow again. Removing a remote server also deletes the OAuth tokens and client registration Claude Code stored for it.
  2. If claude mcp list or /mcp warns about leading or trailing whitespace, edit the entry to remove it, because Claude Code uses the values exactly as written.

Check: claude mcp list shows ✔ Connected next to wireflow, and the test prompt returns your Wireflow account. Scopes and video prompts are in How do I set up an MCP server in Claude Code to generate videos?

What does "Needs authentication" mean for the Wireflow server in Claude Code?

! Needs authentication means Claude Code has the Wireflow server, but you haven't finished signing in, or the server needs you to sign in again.

Cause: Wireflow signs your agent in with OAuth instead of an API key, and that sign-in isn't done. Claude Code also marks a remote server as needing authentication when it drops and needs authorizing again. If wireflow is defined in more than one scope with different endpoints, signing in for one project doesn't cover a project where the other definition loads, because Claude Code stores sign-ins per endpoint.

Fix:

  1. Run /mcp in Claude Code, open wireflow and sign in with your Wireflow account. Approve the permissions on Wireflow's consent screen.
  2. In a claude -p run, sign in with claude mcp login wireflow in your shell, then start the run again.
  3. If claude mcp list warns that wireflow is defined in more than one scope, keep the one you want and remove the others with claude mcp remove wireflow --scope, followed by the scope name.

Check: claude mcp list shows ✔ Connected, and the test prompt returns your Wireflow account.

Why does Claude Code say my MCP server has a "url" but no "type"?

Claude Code reports MCP server "wireflow" has a "url" but no "type"; add "type": "http" (or "sse" / "ws") to this entry when a JSON entry for Wireflow has a url and no type.

Cause: Claude Code reads an entry with no type as a local stdio server, so it skips the entry. This happens when you write the entry yourself in .mcp.json or ~/.claude.json, pass it to claude mcp add-json, or copy an mcpServers block written for another client, such as the Cursor entry for Wireflow, which has only a url.

Fix: Add "type": "http" to the entry. Wireflow's endpoint is Streamable HTTP, and Claude Code also accepts streamable-http as an alias for http:

{
  "mcpServers": {
    "wireflow": {
      "type": "http",
      "url": "https://www.wireflow.ai/api/mcp"
    }
  }
}

Check: claude mcp get wireflow shows the server and its status. Sign in with /mcp if it shows ! Needs authentication, then run the test prompt.

What does "Pending approval" mean for an MCP server in Claude Code?

⏸ Pending approval (run `claude` to approve) means Wireflow is a project-scoped server from .mcp.json that you haven't approved yet, so Claude Code hasn't connected to it.

Cause: Claude Code asks for approval in interactive sessions before it uses project-scoped servers from .mcp.json. In a folder you haven't trusted, approvals committed to the project's .claude/settings.json are ignored, and the server stays pending.

Fix: Run claude interactively in the project, accept the workspace trust dialog, and approve the server. To reset earlier approval choices, run claude mcp reset-project-choices.

Check: claude mcp list no longer shows ⏸ Pending approval for wireflow. Sign in with /mcp if it asks, then run the test prompt.

What does "Disabled for this project" mean in Claude Code?

⊘ Disabled for this project (re-enable via /mcp) means the server is turned off for this project, so Claude Code doesn't connect to it.

Cause: The server was toggled off in the /mcp panel. Claude Code keeps its configuration and records the choice for this project in ~/.claude.json, in the disabledMcpServers list.

Fix: Open /mcp and turn wireflow back on.

Check: The /mcp panel shows a tool count next to wireflow, and the test prompt returns your Wireflow account.

Why does Claude Code say my MCP server disconnected?

Claude Code shows MCP server "wireflow" disconnected · open /mcp to reconnect when the server dropped mid-session and five reconnect attempts failed.

Cause: Claude Code tries to reconnect a dropped remote server up to five times, starting at a one-second delay and doubling it each time. Then it marks the server as failed, or as needing authentication if the server needs authorizing again.

Fix: Open /mcp and retry wireflow from there. To retry every server that failed or needs authentication at once, run /mcp reconnect all, which needs Claude Code v2.1.284 or later.

Check: /mcp shows a tool count next to wireflow, and the test prompt returns your Wireflow account.

Why does Claude Code say "No such tool available" after I resume a session?

A Wireflow tool call fails with No such tool available when you resume a session and the server hasn't connected in time.

Cause: While the server is on its first connection attempt, Claude Code holds the call for up to 10 seconds. If the server doesn't connect in time, or it is already retrying after a failed attempt, the call fails.

Fix: Open /mcp, read the status next to wireflow, and follow the fix for that status on this page. Then ask again.

Check: /mcp shows a tool count next to wireflow, and the test prompt returns your Wireflow account.

Why don't the Wireflow tools appear in Cursor chat?

The Wireflow tools don't appear in Cursor chat when the server is turned off, because disabled servers won't load or appear in chat, or when Cursor can't connect to it.

Cause: A server toggled off in Customize doesn't load. If the server is on, Cursor's MCP logs show the reason: connection errors, authentication issues or server crashes. When a server fails, Cursor shows an error message in chat and marks the tool call as failed.

Fix:

  1. Open Customize in the sidebar, find the Wireflow server, and use its toggle to turn it on.
  2. Check the entry in ~/.cursor/mcp.json, or in .cursor/mcp.json for one project. It needs a wireflow entry under mcpServers with the Wireflow URL:
{
  "mcpServers": {
    "wireflow": {
      "url": "https://www.wireflow.ai/api/mcp"
    }
  }
}

Leave out headers, because Wireflow uses no API key. Leave out the auth object too: it holds static OAuth client credentials for use instead of dynamic client registration, and Wireflow clients register themselves.

  1. If the tools still don't show, open the Output panel (Cmd+Shift+U), select MCP Logs from the dropdown, and look for connection errors, authentication issues or server crashes.

Check: The Wireflow tools are listed under Available Tools, and the test prompt returns your Wireflow account. Full steps are in Cursor setup.

Why won't the Wireflow MCP server connect in Cline?

In Cline, check the Wireflow entry's URL first, as Cline's troubleshooting table says, and set "type": "streamableHttp", because Cline's docs say an entry without type defaults to the legacy SSE transport and Wireflow's endpoint is Streamable HTTP.

Cause: Cline's troubleshooting table answers "Server won't connect" with: verify the command or URL, the server process status and the port. For a remote entry, leaving out type defaults to the legacy sse transport, while Wireflow's endpoint is Streamable HTTP.

Fix:

  1. In the Cline panel, click the MCP Servers icon, open the Configure tab and click Configure MCP Servers. In Cline CLI, the file is ~/.cline/data/settings/cline_mcp_settings.json.
  2. Set the Wireflow entry under mcpServers to this, with no headers, because Wireflow uses no API key:
{
  "mcpServers": {
    "wireflow": {
      "type": "streamableHttp",
      "url": "https://www.wireflow.ai/api/mcp"
    }
  }
}

You can also add it from the Remote Servers tab, with Streamable HTTP as the transport type.

  1. If the Wireflow sign-in didn't finish, run cline mcp in Cline CLI and choose Authorize OAuth to run the browser authorization again.

Check: The Wireflow tools appear, and one tool call works: run the test prompt. In Cline CLI, cline config mcp lists your servers. Full steps are in Cline setup.

For AI agents: the full documentation index is at /llms.txt, and most docs pages are available as Markdown by adding .md to the URL.

© 2026 Wireflow. All rights reserved.