Skip to main content

How do I connect my AI assistant to Wiro with MCP?

Let your AI assistant or code editor search Wiro models, check prices, run them and follow their tasks through Wiro's MCP server, using your own API key.

Wiro's MCP server (Model Context Protocol) lets your AI assistant use Wiro's AI models for you, without leaving the chat or your code editor. Ask in plain words, for example "Generate a photorealistic image of a mountain lake at golden hour", and the assistant finds a suitable model, checks its inputs and price, runs it and brings back the result.

Easiest setup: follow the Wiro MCP Server page of our docs. It has step-by-step guides for Cursor, Claude Code, Claude Desktop, Windsurf, OpenClaw, Hermes and other MCP clients.

What your assistant can do

The server gives your assistant 13 tools, and it picks the right ones for you. It can:

  • Find a model: search the catalog, browse curated picks, or describe your goal and get ranked recommendations.

  • Check inputs and price: read a model's parameters and pricing before running it.

  • Run it: images, video, text, audio, 3D and more.

  • Follow tasks: wait for a long job, check its status, list earlier runs, see what a task cost, cancel a queued task or stop a running one.

  • Extras: upload a file from a link (not from your computer) and search the Wiro docs.

What you need

  • A Wiro account with credit: Wiro is prepaid, so runs are paid from your credit balance. You can add credit in your dashboard.

  • An API key: create a project (see How do I get an API key?). Both project types work, but the credential differs: Signature-Based uses your key and secret, API Key Only uses the key alone. You can switch the type later in the project's settings. The key and secret stay the same, but requests must then use the new type.

  • Node.js 20 or later, only for the local setup (get it from nodejs.org). The hosted server needs nothing installed.

Connect to the hosted server

Most tools connect to Wiro's hosted server with a URL and one header. Using Claude Desktop? Skip to the next section.

  • Server URL: https://mcp.wiro.ai/v1. If your tool asks for a transport, choose Streamable HTTP (or HTTP).

  • Header: Authorization: Bearer YOUR_API_KEY:YOUR_API_SECRET for Signature-Based (used below), or Authorization: Bearer YOUR_API_KEY for API Key Only, as plain text with no encoding.

Cursor: open the command palette (Cmd+Shift+P, or Ctrl+Shift+P on Windows), choose Open MCP settings and add this to mcp.json. Save the file and restart Cursor.

{
"mcpServers": {
"wiro": {
"url": "https://mcp.wiro.ai/v1",
"headers": {
"Authorization": "Bearer YOUR_API_KEY:YOUR_API_SECRET"
}
}
}
}

If "mcpServers" already lists other servers, add only the "wiro" entry inside it, with a comma between entries.

Windsurf: open Settings, then MCP, and add the same entry, but replace "url" with "serverUrl" (see the Windsurf guide).

Claude Code: run this in your terminal, then check with claude mcp get wiro or /mcp:

claude mcp add --transport http wiro https://mcp.wiro.ai/v1 --header "Authorization: Bearer YOUR_API_KEY:YOUR_API_SECRET"

Other MCP clients: any client that supports Streamable HTTP and a custom Authorization header can use the URL and header above. If yours can't add a header but can run a local server, use the local setup below.

Claude Desktop and other local setups

Claude Desktop's Connectors need an OAuth sign-in, which the hosted server doesn't offer yet, so don't paste the URL there. Instead, run Wiro's official open-source package on your computer; it has the same 13 tools. Add this to claude_desktop_config.json (next to any servers already there), then fully quit and reopen Claude Desktop:

{
"mcpServers": {
"wiro": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@wiro-ai/[email protected]"],
"env": {
"WIRO_API_KEY": "YOUR_API_KEY",
"WIRO_API_SECRET": "YOUR_API_SECRET"
}
}
}
}

For API Key Only, delete the WIRO_API_SECRET line and the comma at the end of the line above it. Keep a version number in args (the docs show the current one), so npx doesn't reuse an older cached copy. Full steps: Claude Desktop setup.

Other local clients: any client that can run a local server can use the command npx -y @wiro-ai/[email protected], with WIRO_API_KEY (plus WIRO_API_SECRET for Signature-Based) as environment variables. See Self-Hosted MCP.

Good to know

  • Billing: the MCP server is free. You pay standard Wiro prices for the models you run, and only successful tasks are billed.

  • Long jobs: each wait lasts up to 45 seconds. If a job such as a video takes longer, your assistant can keep waiting on the same task at no extra cost. Don't ask it to run the request again: that starts a second task, billed separately if it succeeds.

  • History: when your assistant lists earlier runs, it sees recent runs from your whole Wiro account, including the website, not just this project. For a team project, it sees the team's runs.

  • MCP vs. LLM Gateway: MCP lets your assistant find and run Wiro models. The LLM Gateway lets your coding tool use a Wiro chat model as its AI.

  • Your key: the hosted server never stores it, but your config file does, so never share that file or put it in public code or repositories.

Troubleshooting

  • The Wiro tools don't appear, or you see "Missing or invalid Authorization header": check that the URL is https://mcp.wiro.ai/v1 and the header starts with Bearer and a space, then fully quit and reopen your client. For the local setup, check that node --version shows 20 or later.

  • Running a model or checking a task fails with "Project authorization..." or "Project requires signature authentication": the credential doesn't match the project (searching models can still work with a wrong key). "...is not founded" means the key is wrong, "...is not valid" means the secret is wrong, and "requires signature authentication" means a Signature-Based project is missing its secret. You never add x-signature or x-nonce headers yourself.

  • "Requested ip ... is not allowed": the project's IP whitelist blocks the request. Use a project with no IP whitelist.

  • Claude Desktop says "Not valid MCP server configurations", or every call fails at once: make sure the entry has "type": "stdio", command, args (with the version number) and env as shown, then fully quit and reopen Claude Desktop.

  • "Insufficient balance" or "You have reached your concurrent task limit": add credit, or wait for a running task to finish. See How many tasks can I run at the same time?

  • "Rate limit exceeded": the hosted server limits how many requests one key can send per minute, and every step your assistant takes counts. Wait a minute, then try again.

Did this answer your question?