Wireflow ships an MCP (Model Context Protocol) server that exposes every workflow you build as a callable tool for AI agents. Plug it into Claude Desktop, Cursor, or any MCP-compatible client and your workflows become first-class agent capabilities.

Server endpoint

POST https://www.wireflow.ai/api/mcp

Transport: streamable-http Authorization: OAuth 2.0 (metadata at /.well-known/oauth-protected-resource)

The server card is published at /.well-known/mcp/server-card.json for auto-discovery.

What the server exposes

• Tools for every workflow the authenticated user can execute
• Resources for workflow outputs (images, video, audio URLs)
• Prompts for common pipelines (text-to-image, image-to-video, remix)

Tool definitions are generated from each workflow's input port schema, so the client sees typed parameters (string, image URL, video URL, number, boolean) rather than a generic opaque blob.

Claude Desktop setup

Add Wireflow to your Claude Desktop claude_desktop_config.json:

{
  "mcpServers": {
    "wireflow": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.wireflow.ai/api/mcp"]
    }
  }
}

Restart Claude Desktop. You'll be prompted to authorize via OAuth on first use. After that, Claude can call any of your workflows directly from a conversation.

Cursor setup

In Cursor, open the MCP settings and add:

{
  "wireflow": {
    "url": "https://www.wireflow.ai/api/mcp"
  }
}

Custom clients

The server implements MCP spec v2024-11-05 with streamable-http transport. Any client that speaks MCP should work — start from the agent-skills index to discover available skills, then authorize via OAuth2.

Why MCP?

MCP eliminates the "API wrapper sprawl" problem — instead of building a new integration for every AI product, your agent discovers Wireflow's capabilities through /.well-known/ endpoints and calls them with typed parameters. The same workflow you build visually is immediately usable by Claude, Cursor, or any future MCP client with zero extra code.

Related

• REST API reference — if you're integrating without MCP
• Webhook triggers — for cron-style or Zapier-style triggers
• Publishing apps — expose a workflow as a branded web app with credit billing