MCP Servers PRO

Requires HTTPBot Pro.

The Model Context Protocol (MCP) is an open standard that lets AI applications connect to servers exposing tools (callable functions), resources (readable data) and prompts (reusable message templates). HTTPBot acts as an MCP client and test harness: connect to any MCP server over HTTP, browse what it offers, invoke tools with your own arguments, and inspect the raw JSON-RPC traffic — no AI model involved, and nothing is sent anywhere except to the server you configure.

Find it in the MCP tab on iPhone, or the MCP Servers sidebar section on iPad and Mac.

Adding a server

Tap + in the MCP tab (iPhone) or Add Server in the sidebar section (iPad and Mac) and fill in:

• Name — a label for the list.
• URL — the server's HTTP endpoint (for example https://example.com/mcp).
• Transport — Streamable HTTP (the current MCP standard) or HTTP + SSE (Legacy) for older servers.
• Headers — custom headers sent with every request in the session.
• Auth — None, Bearer Token, API Key, or OAuth 2.0 (including the built-in Get Access Token flow). Credentials are attached to every request in the session, exactly like request auth.

Server configurations sync across your devices via iCloud, but credentials never leave the device — after sync, re-enter the token or secret once on each device.

Connecting and browsing

Opening a server connects automatically and performs the MCP handshake. The status header shows the connection state plus the server's name and version. Once connected, the segmented tabs fill in:

• Tools — every tool with its description. Tap one to invoke it.
• Resources — readable items by URI. Tap one to fetch and view its contents.
• Prompts — prompt templates with their arguments. Tap one to fill in the arguments and fetch the rendered messages.

The last listing is cached, so you can browse a server's catalog while offline; reconnecting refreshes it.

Sessions stay alive while the app runs: navigating away and reopening a server reuses the live session, so servers that authorize the session itself (see below) don't ask you to log in again on every visit. A session ends when you choose Disconnect from the toolbar menu, when you edit the server's configuration, or when the app quits. (Servers may also expire sessions on their own schedule — if that happens, the next call fails and Reconnect starts a fresh session.)

Invoking a tool

HTTPBot builds a native form from the tool's input schema: text fields for strings and numbers, switches for booleans, pickers for enumerations, and comma-separated lists for arrays. Required fields are marked, and values are validated against the schema before sending.

Prefer raw JSON — or using a tool whose schema is too complex for a form (nested objects, oneOf/anyOf, $ref)? Toggle to the JSON editor to write the arguments object directly; the form's current values carry over.

Tapping a tool opens its form, and the result appears in its own view — beside the form on larger screens, or as a sheet you can dismiss and reopen on iPhone. Text renders in full as markdown, with tappable links that open in the system's in-app sign-in sheet rather than switching you out to Safari. That matters for servers whose login flow is itself a tool returning an authorization link — tap it, sign in, close the sheet, and the session is authorized from then on. JSON, XML and HTML payloads render directly in the full pretty-printed viewer; HTML adds a Raw / Preview toggle so you can switch between the source and a rendered page. Images, embedded resources and resource links render inline. A Success or Error status pill in the result view reflects whether the server flagged the result as an error (isError).

The wire inspector

The Wire tab shows every JSON-RPC frame in the session — requests, responses and server notifications — with direction, method and timestamp. Tap a frame to see the full, pretty-printed JSON. This is the fastest way to debug a misbehaving MCP server: you see exactly what went over the wire, byte for byte.