RequestTailor Preview (22 November 2026): requests as files in Git, no account, offline – on the Mac, in the browser and in the pipeline. What’s inside → +43 664 1964199Contact →

MCP client

If you build an MCP server, you want to test it like an API: connect, call tools, check the result – and keep the call as a test. RequestTailor’s MCP client does exactly that. Saved tests are readable files next to your collection, variables and secrets work as for requests, and rt mcp-test runs them in the pipeline.

Edition
Free
Where
MCP tab in the sidebar
Transports
Streamable HTTP everywhere, stdio on the Mac and in rt
Tests
companion files *.mcp.yaml
Pipeline
rt mcp-test, exit code 4 on failure

Connect to a server

The MCP tab in the sidebar opens the MCP client; New connection starts a new connection.

MCP client connected to demo-mcp 1.0.0 over Streamable HTTP at http://localhost:3333/mcp, protocol 2025-11-25, environment Local; on the left the tools echo (read-only), add, fail and image, on the right the tool add with JSON arguments, Call tool, Save as test… and the result OK with sum 5
Connected to a demo server: pick a tool, enter the arguments, Call tool.
  1. Transport: Streamable HTTP with the Server URL (and headers, for example for a token) or stdio with Command, arguments and environment variables. stdio starts a local process and is therefore available only in the Mac app and in rt, not in the web app.
  2. After connecting: the server’s name and version, the negotiated protocol version and the selected environment.
  3. The list of Tools with descriptions; the server can mark tools as read-only.
  4. You enter arguments in the Form built from the tool’s input schema, or directly as JSON.
  5. Call tool calls the tool. The result shows status and time, the structured output and the raw content.

{{variables}} in the server address, headers, command and arguments are resolved from the selected environment. Secret values appear as *** in the result – error messages included.

Save calls as tests

  1. Call the tool with the arguments you want.
  2. Click Save as test…, give it a name and add assertions on the result: Expression, Operator, Expected value – with the same operators as for requests.
  3. Save in the header writes the test file into the collection. The test appears under Saved tests; Run runs it, Run all runs all of them.
  4. When something changes, call the tool again and take it over with Update test….
MCP client with the test mcp/add-numbers.mcp.yaml open: in the sidebar Saved tests with 1 passed, 0 failed and the green test add-numbers with Run; on the right the call of add with Update test… and the result sum 5
A saved test is a file in the collection and runs with one click.

For assertions, res.status is 200, or 500 for a tool error; res.body is the structured output, otherwise the first text. A test without assertions fails when the tool reports an error.

The test file

Each test is a companion file <name>.mcp.yaml. Because the collection reader reads only .yml files, tests never show up as requests. The file is written in a stable way, so diffs show only what changed:

name: Echo says hello
server:
  transport: http
  url: "{{mcpUrl}}"
  headers:
    - name: Authorization
      value: "Bearer {{token}}"
tool: echo
arguments:
  text: hello
assertions:
  - expression: res.body.text
    operator: eq
    value: hello

A stdio server has the fields command, args, env and optionally cwd instead of url and headers. Secret values never belong in the file, only references such as {{token}}; the app checks that before saving.

In the pipeline: rt mcp-test

rt mcp-test                         # every test of the collection you are in
rt mcp-test mcp/ -e Staging --var token=$MCP_TOKEN

Paths are test files or folders of one collection. Tests run one after the other, each with its own connection; stdio servers start in the collection folder. Output: JSON on stdout with all results, passed and failed, secrets as ***, plus one line per test on stderr.

Exit codeMeaning
0All tests passed
1A server could not be reached or started (takes precedence)
2Bad arguments or no tests found
3External secrets could not be read
4A test failed: an assertion, a tool error or an unreadable test file

See also

Sources on this page

The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.

  1. 1

    MCP client with saved tests ↑Product · RequestTailor core repository, crates/rt-app (mcp_client), crates/rt-cli/src/mcp_test.rs · checked on 2026-11-22

Frequently asked

Short answers.

Does the MCP client work in the web app too?
Yes, with Streamable HTTP. stdio servers start a local process; that works only in the Mac app and with rt mcp-test on the command line.
Are my tokens in the test file?
No. The file holds only references to variables; the values come from the environment, the keychain or --var when the test runs. The app checks before saving that no secret value ends up in the file.
Which MCP protocol version does the client speak?
It negotiates the version with the server when connecting and shows it afterwards, together with the server’s name and version.

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch

Contact

Requests in the repo instead of an account? Talk to us.

Free is free and stays free. For an early copy, for Enterprise, for the OData plugin on your SAP system or for a wish for Pro and Team: write to me. I reply within one working day, personally.

Martin KochManaging Director, CloudDNAI read every request myself and reply personally.