Skip to content
Wire Docs

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.

What is MCP?

Section titled “What is MCP?”

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.

Wire’s MCP server

Section titled “Wire’s MCP server”

Each Wire container has its own MCP server:

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

File downloads

Section titled “File downloads”

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, for 2 credits per download. See File downloads (Resources) for the full flow.

If an agent installed on the container brings usage guidance, the container also sends its instructions when a client connects and serves its skill as a skill:// resource. Both are free to read. See Skills and instructions.

If an installed agent ships interactive views, the container serves each one as a ui:// resource over MCP Apps, and clients that support it, such as Claude, ChatGPT, VS Code, and Goose, show the view next to the tool’s result. Reading a view is free. See Interactive views (MCP Apps).

Supported clients

Section titled “Supported clients”

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.

A few tools sit outside that set and are off on MCP by default: the file and status tools serve REST only, and wire_query, which runs read-only SQL over a container’s structured objects, is off on both transports until an organization owner or admin enables it for the container. Anything switched off is absent from tools/list, so agents never see it.

REST

Section titled “REST”

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).

Next Steps

Section titled “Next Steps”