Wiro AI

Wiro MCP Server

Official MCP server for Wiro AI: run image, video, audio and LLM models, build and run workflows, and deploy and talk to AI agents from Cursor, Claude Code, Claude Desktop, Windsurf and any other MCP client.

Website · Models · Docs · Dashboard

@wiro-ai/wiro-mcp is a TypeScript Model Context Protocol server that runs locally over stdio, with npx or Docker. Its tools are grouped in three sets:

• Models: search the Wiro AI model catalog, read a model's parameters and price, run it and wait for the result, upload input files and browse past tasks.
• Workflows: build multi-step workflows that chain models, run them, resume failed runs, browse the public gallery, and design workflows together with the Workflow Agent.
• Agents: talk to Studio, the creative agent that runs models for you, and deploy, configure, run and message your own agents built from templates or from scratch.

Playbooks explain each job step by step, so the assistant knows the order of calls, what costs money and what needs your approval. The hosted server at https://mcp.wiro.ai/v1 serves the same tools with nothing to install.

Quick Start

Local npx and library usage require Node.js 20 or later. The hosted MCP endpoint and the Docker image do not require a local Node.js installation.

1. Get API Keys

Sign up at wiro.ai and create a project at wiro.ai/panel/project/new to get your API key and secret.

2. Add to Your AI Assistant

Cursor: open MCP settings (Cmd+Shift+P → "Open MCP settings") and add:

{

"mcpServers": { "wiro": { "command": "npx", "args": ["-y", "@wiro-ai/wiro-mcp"], "env": { "WIRO_API_KEY": "your-api-key", "WIRO_API_SECRET": "your-api-secret" } } } }

Claude Code:

claude mcp add wiro -- npx -y @wiro-ai/wiro-mcp

Then set environment variables WIRO_API_KEY and WIRO_API_SECRET.

Claude Desktop: add to claude_desktop_config.json:

{

"mcpServers": { "wiro": { "type": "stdio", "command": "npx", "args": ["-y", "@wiro-ai/wiro-mcp"], "env": { "WIRO_API_KEY": "your-api-key", "WIRO_API_SECRET": "your-api-secret" } } } }

Windsurf: add to MCP settings:

{

"mcpServers": { "wiro": { "command": "npx", "args": ["-y", "@wiro-ai/wiro-mcp"], "env": { "WIRO_API_KEY": "your-api-key", "WIRO_API_SECRET": "your-api-secret" } } } }

OpenClaw: configure a remote server under mcp.servers:

{

"mcp": { "servers": { "wiro": { "url": "https://mcp.wiro.ai/v1", "transport": "streamable-http", "connectionTimeoutMs": 10000, "headers": { "Authorization": "Bearer ${WIRO_MCP_AUTH}" } } } } }

Set WIRO_MCP_AUTH in OpenClaw's environment to your API key, or to API_KEY:API_SECRET for a project with signature-based auth. Then verify with openclaw mcp doctor wiro --probe. On older OpenClaw releases without that probe command, use openclaw mcp show wiro, restart OpenClaw, and run /tools verbose.

Hermes: add to ~/.hermes/config.yaml:

mcp_servers:

wiro: url: "https://mcp.wiro.ai/v1" headers: Authorization: "Bearer ${WIRO_MCP_AUTH}" timeout: 60 connect_timeout: 10

Store WIRO_MCP_AUTH (your API key, or API_KEY:API_SECRET) in ~/.hermes/.env, then run /reload-mcp and /tools.

3. Start Using

Ask your AI assistant:

Models

• *"Generate a photorealistic image of a mountain lake at sunset"*
• *"What video generation models are available on Wiro?"*
• *"Show me the parameters for google/veo3-1"*
• *"Create a 5-second video with Kling V3: a drone shot over mountains"*
• *"Check the status of my last task"*
• *"Show my latest productions and open the newest result"*

Workflows

• *"Build a workflow that turns a product photo into a short ad video, then run it on this photo"*
• *"Find a public workflow for podcast covers and run it with my show's name"*
• *"Ask the Workflow Agent to add an upscale step to my product ad workflow and save it"*
• *"Why did my last workflow run fail? Resume it if it can be resumed"*

Agents

• *"Ask Studio for three logo ideas for a coffee shop"*
• *"Which agent templates can manage Instagram? What does each plan cost?"*
• *"Deploy the Instagram manager agent on the Starter plan and tell me what it still needs"*
• *"Tell my support agent to summarise today's tickets"*

Docker

Every release is also published on Docker Hub as wiroai/wiro-mcp, for linux/amd64 and linux/arm64. The image runs the same stdio server, so you need Docker but not Node.js:

docker run -i --rm -e WIRO_API_KEY wiroai/wiro-mcp

-e WIRO_API_KEY hands the variable from your environment to the container. For a project with signature-based auth, add -e WIRO_API_SECRET as well. WIRO_TOOLSETS passes through the same way. Keep -i, since the server reads its requests from stdin, and leave out -t.

In a client config, docker is the command and the credentials go in env. This works in Cursor, Claude Desktop and Windsurf:

{

"mcpServers": { "wiro": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "WIRO_API_KEY", "-e", "WIRO_API_SECRET", "wiroai/wiro-mcp"], "env": { "WIRO_API_KEY": "your-api-key", "WIRO_API_SECRET": "your-api-secret" } } } }

Claude Code:

claude mcp add wiro -e WIRO_API_KEY=your-api-key -e WIRO_API_SECRET=your-api-secret -- docker run -i --rm -e WIRO_API_KEY -e WIRO_API_SECRET wiroai/wiro-mcp

For an API Key Only project, leave out the WIRO_API_SECRET value. Docker only passes variables that are set, so the -e WIRO_API_SECRET argument can stay.

Image tags follow the npm versions: wiroai/wiro-mcp: pins a release and latest is the newest one. A client does not fetch a newer latest by itself, so run docker pull wiroai/wiro-mcp to update. Pulling once before the first start also means the client does not wait for the download.

Authentication

Wiro AI supports two authentication types, chosen when you create a project:

Signature-Based (Recommended)

More secure. Requires both API key and API secret.

WIRO_API_KEY=your-api-key

WIRO_API_SECRET=your-api-secret

API Key Only

Simpler. Only requires the API key. Omit WIRO_API_SECRET from your config.

WIRO_API_KEY=your-api-key

The hosted server takes the same credentials as a bearer token: Authorization: Bearer API_KEY:API_SECRET for a signature-based project, or Authorization: Bearer API_KEY for an API Key Only project.

Available Tools

Models

For long generations, run_model returns the existing task ID and token when its wait budget expires. The assistant must continue with wait_for_task; retrying run_model creates a separate billable task.

Workflows

A workflow chains models and built-in utility steps into one graph with its own inputs and outputs. Every model step is charged like a normal model run when it finishes. Wiro fills a model input you leave out with the model's default, so the save result lists what it filled, and a graph can be at most 40 KB of JSON.

The Workflow Agent designs workflows with you in plain language: talk to it with send_agent_message and agent: "workflow-agent", attach an existing workflow to edit, then save its proposal with save_workflow_from_agent. Conversations started through this server belong to the connected project and are separate from your Workflow Agent chats on wiro.ai.

Agents

Talk to any Wiro agent with one set of tools. agent is "studio", "workflow-agent" or the id of one of your own agents. Session names use letters, digits, dots, dashes, underscores and colons, up to 128 characters (100 for the Workflow Agent), and cannot end in "-r" followed by a number. Studio refuses a message under any other name; a session it has under another name can be read and deleted, and to go on with it you start a new session.

| delete_agent_session | Delete a conversatio