MCP Requests

MCP Requests

Getman can act as a Model Context Protocol (MCP) client: connect to an MCP server, browse the tools it exposes, and call a tool with JSON arguments — all from a request tab, much like an HTTP request.

This first version is tools-only over the Streamable HTTP transport.

Switching a tab to MCP

Choose MCP in the request-kind selector (next to the method, in the URL bar). As with WebSocket/SSE, the SEND button is replaced by a CONNECT button (which becomes DISCONNECT/STOP, shown in red, while connected).

1. Enter the server's endpoint URL (an http(s):// Streamable HTTP endpoint, e.g. https://example.com/mcp).
2. If the server needs auth, add a header in the Building Requests (e.g. Authorization: Bearer …).
3. Click CONNECT. Getman performs the MCP initialize handshake and lists the server's tools.

The endpoint URL and header values are resolved for {{variables}} (and trimmed) before connecting.

Calling a tool

Once connected, the panel shows:

• Tools (N) — a chip per advertised tool. Tap one to select it.
• Input schema — the selected tool's JSON Schema, shown read-only for reference.
• Arguments (JSON) — an editor where you type the call arguments as a JSON object. It supports the same {{variable}} highlighting and {{ autocomplete as the request body, and resolves environment and dynamic variables (e.g. {{$guid}}) at call time. Invalid JSON shows an inline error and the call is not sent.
• CALL — sends the call (shows CALLING… while in flight).
• Result — the tool's response, rendered as formatted, syntax-highlighted JSON. An error result is headed Result (error) in red.
• Session log — a collapsible log of the JSON-RPC traffic for the session.

Click DISCONNECT to close the session.

Saving MCP requests

An MCP request can be saved into a Collections like any other. In the tree it carries an MCP badge (instead of an HTTP method), the same way WebSocket/SSE requests show WS/SSE.

Current limits

• Tools only — resources and prompts are not yet supported.
• HTTP transport only — remote Streamable HTTP servers. Local (stdio) servers are not supported.
• No server-initiated messages — there are no subscriptions/notifications; each call is a request/response.
• MCP traffic is not recorded in History or response time-travel (it's a separate protocol). The endpoint URL, kind, and headers persist with the tab.

See also Realtime WebSocket and SSE and FAQ and Troubleshooting.