Wireflow AI
Wireflow speaks the Model Context Protocol. Connect Claude or any MCP client and let it build, inspect, and run your AI workflows, and generate and edit media through one canvas, API, and MCP, across 100+ models. It acts on your behalf with explicit consent and per-scope permissions. Add a custom connector in your MCP client and point it at the Streamable HTTP endpoint below. The client walks you through Wireflow’s OAuth sign-in and a consent screen, no manual API keys, no client setup. - OAuth 2.1 authorization code flow with PKCE (S256). - Dynamic Client Registration (RFC 7591), so clients self-register with no pre-shared credentials. - You approve a consent screen listing exactly the permissions the client asked for. Revoke anytime from settings.
Ads
Overview
Wireflow speaks the Model Context Protocol. Connect Claude or any MCP client and let it build, inspect, and run your AI workflows, and generate and edit media through one canvas, API, and MCP, across 100+ models. It acts on your behalf with explicit consent and per-scope permissions. Add a custom connector in your MCP client and point it at the Streamable HTTP endpoint below. The client walks you through Wireflow’s OAuth sign-in and a consent screen, no manual API keys, no client setup. - OAuth 2.1 authorization code flow with PKCE (S256). - Dynamic Client Registration (RFC 7591), so clients self-register with no pre-shared credentials. - You approve a consent screen listing exactly the permissions the client asked for. Revoke anytime from settings.
Capabilities
- list_workflows
Inspect workflows — Ask to list your workflows with `list_workflows` or drill into a specific graph's nodes and inputs via `get_workflow`.
- create_workflow_from_prompt
Build from a prompt — Have `create_workflow_from_prompt` draft a new workflow from a description, then refine node configs with `update_workflow_config`.
- get_video_timeline
Preview and edit video — Use `get_video_timeline` to inspect scenes, `preview_video_frames` for free stills, and `edit_video_timeline` to swap cuts before rendering.
- run_workflow
Run and monitor jobs — Trigger `run_workflow` to get an executionId, then poll `get_execution` for status and output URLs.
- list_automations
Manage automations — List, create, pause, or reschedule recurring runs via `list_automations`, `create_automation`, and `update_automation`.
- whoami
Check account state — Confirm identity with `whoami`, view credit balance via `get_credit_balance`, or browse available models with `list_models`.
Installation
https://www.wireflow.ai/docs/mcp
Configuration
{
"mcpServers": {
"wireflow-ai-mcp": {
"url": "https://www.wireflow.ai/docs/mcp"
}
}
}Paste into ~/.cursor/mcp.json or .cursor/mcp.json
Tags
- documentation
- document
- video
- content-creation
- design
Related MCP servers
Architecture & Design
SVGator MCP
The MCP server connects your AI assistant straight to SVGator, the online SVG animation tool. From there, your assistant can work inside your projects to browse, inspect, edit, create, and export them for you, handling everything from a simple “edit colors according to this brand kit” to a complete “build me an animated logo reveal and export it as a CSS-only file.” - Endpoint: https://mcp.svgator.com/mcp - Protocol: Model Context Protocol over Streamable HTTP - Authentication: OAuth 2.1 (sign in with your SVGator account — see Getting started)
6 tools · create_project, edit_part
Architecture & Design
Compeller
The Compeller MCP endpoint implements the Model Context Protocol as a thin JSON-RPC 2.0 wrapper over the existing v1 REST API. It is intended for agent integrators (Claude Desktop, Cursor, custom MCP clients, DigiRAMP) that speak MCP natively rather than raw HTTP. - Transport: Streamable HTTP (single JSON-RPC message per HTTP POST). - URL: POST https://compeller.ai/api/mcp - Protocol version: 2024-11-05 - Server name / version: compeller-mcp / see initialize result. - Tool contract: The tool list below is the public integration contract. Use tools/list for the runtime-advertised set on the deployed server. - Directory listings: Official MCP Registry · Smithery · Glama
6 tools · get_account_credits, get_compel
Architecture & Design
Rive MCP
> Note > > MCP integration is currently available only in the desktop Editor for Windows and macOS. You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of states/layers, Layouts, Shapes, and more. Create and manage Rive files — add, rename, resize, arrange, and focus artboards. Inspect and edit the scene — query hierarchies, select objects, update properties, rename, duplicate, reorder, reparent, or delete elements. Build designs — create shapes, paths, layouts, component instances, component lists, and asset-based elements. Create animation and interaction — edit linear animations, state machines, states, transitions, conditions, keyframes, and interpolation. Work with data binding — create view models, properties, instances, bindings, and custom property groups. Edit scripts and shaders — manage Luau scripts and WGSL shad
6 tools · Build designs, Create and manage Rive files
Architecture & Design
Inkrun MCP
Inkrun turns Markdown into consistently themed PDFs. Reach the render pipeline two ways — a REST API, or an MCP server your agent calls directly — plus a dashboard for authoring templates and themes. Add Inkrun as a custom connector in Claude Desktop over OAuth — no API key. ](https://inkrun.dev/docs/mcp/claude-desktop)[ Add Inkrun as a custom connector on claude.ai over OAuth — no API key. ](https://inkrun.dev/docs/mcp/claude-ai)[ Connect any other MCP client — over OAuth, or with an API key sent as a header.
5 tools · Extract structured data, Extract tables from PDFs
Architecture & Design
Lottie Creator MCP
The Lottie Creator MCP brings your AI assistant directly into your animation workflow — giving it full access to LottieFiles Creator so it can build and edit Lottie animations on your behalf through natural language. You can check out the installation further down. MCP servers are part of a standardized interface for AI agents to interact with data sources using the Model Context Protocol. The Lottie Creator MCP connects AI assistants like Claude, Cursor, and Windsurf to the Creator API through a local bridge — meaning your AI gets the same full access to Creator that you do.
5 tools · Analyze for accessibility and brand, Batch generate animation variants
Architecture & Design
Picsart GenAI MCP
The Picsart MCP server exposes the full model catalog as Model Context Protocol tools. Connect it to any MCP-compatible agent and that agent can generate image, video, and audio across 178 models using natural language or structured tool calls. New to MCP? Start with What is MCP? first. 1. Install the gen-ai CLI — see Installation. 2. Run gen-ai login once (opens your browser for OAuth). That is all. The MCP server (gen-ai-mcp) ships with the CLI and uses the same credentials. > "Generate a product image on a white background using Flux 2 Pro, 4:3 aspect ratio."
5 tools · picsart_drive, picsart_generate
Architecture & Design
Eagle MCP
Eagle MCP Server is a local Model Context Protocol bridge that lets AI assistants (e.g. Cursor, Claude) access your Eagle media library so you can tag, categorize, search, and batch-organize assets with natural language.
Architecture & Design
Blender MCP
A lightweight MCP (Model Context Protocol) server for Blender. It offers a natural language interface with Blender’s Python API, improving access to documentation, and allowing users to explore and understand complex setups. For technical details and documentation about the architecture check the source code. > [!warning] Warning > Security Warning > The MCP server will execute LLM generated code in Blender without any guards in place to protect your data from removal or being sent to a remote location. To keep your data safe it is recommended to use a virtual machine, or a system without access to sensitive information.
5 tools · Data-block renaming, Geometry Nodes documentation