Skip to content

Overview

Wire containers expose a fixed set of tools. MCP and REST are two transports for invoking those tools — pick whichever fits the calling environment. The Tools page is the source of truth for what each tool does, its parameters, its output shape, and its default visibility on each transport.

  • MCP (Model Context Protocol) — Connect AI tools like Claude, Cursor, and Cline directly to your containers. The primary access path for agents.
  • REST API — Plain HTTP for automation, CI/CD pipelines, webhook-style integrations, and any caller that can make an authenticated POST.

MCP (Model Context Protocol) is an open standard that lets AI tools connect to external data sources. Wire uses MCP so you can access your containers from Claude, Cursor, and other compatible tools.

Each Wire container has its own MCP server:

This URL is shown on your container’s detail page in the Wire dashboard.

Beyond tools, Wire containers also expose uploaded files as MCP resources under the wire://container/{id}/file/{fileId} scheme. Agents can download the original bytes of any file — PDFs, CSVs, images, audio — via resources/read. See File downloads (Resources) for the full flow.

We have setup guides for these clients:

Wire follows MCP standards, so it should work with any MCP-compatible client.

Containers are ready for MCP connections immediately after creation — the standard 5 (wire_explore, wire_search, wire_navigate, wire_write, wire_delete) are available without any file uploads or analysis.

REST gives you the same tools over plain HTTP. Useful for automation, CI/CD pipelines, webhook integrations, and any caller that can make an authenticated POST. See the REST API page for transport details (base URL, auth, dispatcher pattern, error codes).