Self-Hosted MCP

Quick Start

Add to your AI assistant's MCP config:

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

That's it. Your assistant can now run Wiro models, build and run workflows, and work with Studio and your own agents. The args entry pins the current published version (@wiro-ai/wiro-mcp@1.5.0) so npx does not reuse an older cached build.

Setup

Add the self-hosted MCP server to your AI assistant:

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

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

export WIRO_API_KEY="your-api-key"
export WIRO_API_SECRET="your-api-secret"

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

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

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

extensions:
  wiro:
    name: Wiro AI
    type: stdio
    cmd: npx
    args: ["-y", "@wiro-ai/wiro-mcp@1.5.0"]
    envs:
      WIRO_API_KEY: your-api-key
      WIRO_API_SECRET: your-api-secret
    enabled: true
    timeout: 300

npx -y @wiro-ai/wiro-mcp@1.5.0

Authentication

Signature-Based (Recommended)

Provide both API key and secret:

WIRO_API_KEY=your-api-key
WIRO_API_SECRET=your-api-secret

API Key Only

Omit WIRO_API_SECRET:

WIRO_API_KEY=your-api-key

Authentication errors

If the project uses signature-based auth and WIRO_API_SECRET is not set, tool calls fail with:

Wiro API error 401: This project uses signature-based auth. Set WIRO_API_SECRET to the project's API secret in your MCP server config.

Add WIRO_API_SECRET to the env block of your MCP config and restart the client. The other messages are the same as on the hosted server: see Authentication errors.

Available Tools

The self-hosted server provides the same 50 typed tools, playbooks and prompts as the hosted MCP server. Successful calls include structuredContent for LLM chaining plus text content for compatibility. Completed media calls return standard MCP resource links and an assistant-audience delivery instruction so the assistant can present image previews and clickable media links in its user-facing response even when the client does not render media inside its tool card.

All three tool groups load by default. To load fewer tools, set WIRO_TOOLSETS (see Environment Variables). get_account, get_playbook and search_docs are always available.

Model slugs: Use the clean/lowercase format owner/model (e.g. openai/sora-2, wiro/virtual-try-on). These correspond to cleanslugowner/cleanslugproject values returned by search_models.

Models

Workflows

Agents

The conversation tools call the matching Message/* route of Studio (/Studio/), the Workflow Agent (/StudioWorkflow/) or a deployed agent (/UserAgent/), chosen by their agent argument.

Account and guides

See the Wiro MCP Server page for the playbook topics, the prompts, the rules for paid and irreversible actions, and the tool arguments.

Environment Variables

Choosing tool groups

Some clients work best with fewer tools. Set WIRO_TOOLSETS to load only the groups you need:

"env": {
  "WIRO_API_KEY": "your-api-key",
  "WIRO_TOOLSETS": "models,workflows"
}

get_account, get_playbook and search_docs are always available, and workflows also brings the model search tools it needs. The conversation tools for Studio and the Workflow Agent, with save_workflow_from_agent, come with either workflows or agents, and each prompt appears only when its tools are loaded. If a job needs a tool from a group that is not loaded, the server instructions tell the assistant to say so.

GitHub & npm

• GitHub: github.com/wiroai/Wiro-MCP
• npm: @wiro-ai/wiro-mcp

Using as a Library

import { WiroClient } from '@wiro-ai/wiro-mcp/client';
import { createMcpServer } from '@wiro-ai/wiro-mcp/server';

const client = new WiroClient('your-api-key', 'your-api-secret');
const server = createMcpServer(client);

// Only the model and workflow tools
const modelsAndWorkflows = createMcpServer(client, { toolsets: ['models', 'workflows'] });

Self-Hosting on Your Server

git clone https://github.com/wiroai/Wiro-MCP.git
cd Wiro-MCP
npm install
npm run build
export WIRO_API_KEY="your-api-key"
export WIRO_API_SECRET="your-api-secret"
node dist/index.js

Requires Node.js 20 or later. Create a project to get API keys.