wiroai/wiro-mcp repository overview

⁠Wiro MCP Server

Official MCP server for Wiro AI: search and run 1,000+ 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.

This image runs the open-source stdio server @wiro-ai/wiro-mcp⁠, built from github.com/wiroai/Wiro-MCP⁠. Every release is published for linux/amd64 and linux/arm64, so you need Docker but not Node.js.

⁠Quick start

Create a project at wiro.ai/panel/project/new⁠ to get an API key, plus an API secret if the project uses signature-based auth. Then:

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. Keep -i, since the server reads its requests from stdin, and leave out -t.

⁠Client config

In Cursor, Claude Desktop and Windsurf, docker is the command and the credentials go in env:

{
  "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.

⁠Environment variables

⁠What it can do

• 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.
• Account and guides: get_account, get_playbook and search_docs are always on.

Playbooks explain each job step by step, so the assistant knows the order of calls, what costs money and what needs your approval. Tools that charge your wallet, such as agent plans and credit packs, first return the price and act only after you agree.

⁠Tags

Tags follow the npm versions: wiroai/wiro-mcp:<version> 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.

⁠About the image

• Based on node:24-alpine and runs as the non-root node user (uid 1000).
• Built from source with the repository's lockfile. Each release carries build provenance and an SBOM.
• No ports and no volumes: the server talks over stdin and stdout and calls https://api.wiro.ai/v1.

The same tools are also hosted at https://mcp.wiro.ai/v1 over Streamable HTTP, with nothing to run locally. The MCP Server docs⁠ have setup steps for each client.

⁠Links

Website⁠ · Models⁠ · Docs⁠ · GitHub⁠ · npm⁠ · Dashboard⁠

⁠License

MIT, see LICENSE⁠.