Introducing Thunder Client MCP Server v2

We’re adding new capabilities to our MCP server with Thunder Client MCP Server v2. AI tools like Claude Code, GitHub Copilot, Cursor and Codex can now work directly with your Thunder Client collections: build requests, run tests and fix failures, right from the chat. One-command setup, with no API keys, tokens or OAuth to configure.

Install: Thunder Client MCP documentation

Key features

12 tools for your AI assistant to work with Thunder Client
Generate collections from your source code
Create and edit requests, including from a curl command
Add tests and scripts to your requests
Run requests and collections, fix failures and generate reports

Requirements

Node 22 or higher
The Thunder Client extension, updated to the latest version

Installation

Install for Claude Code:
claude mcp add thunderclient -- npx -y thunderclient-mcp
Install for Codex:
codex mcp add thunderclient -- npx -y thunderclient-mcp
Copilot Chat, Cursor, Antigravity and Kiro: add the server to your MCP config file. See Installation.
Note: the Thunder Client CLI is installed automatically with the MCP server.

Build collections

Example: “Create a collection called Orders API from the Express routes in src/routes, with one folder per resource.”
Example: “Import every endpoint from openapi.yaml into a Petstore collection, grouped by tag.”

Screen recording: the prompt is sent in Claude Code, and the Orders API collection with Orders, Customers and Products folders appears in the Thunder Client sidebar — Claude Code builds the Orders API collection from the Express routes

The new collection shows up in the Thunder Client sidebar right away, with one folder per resource and sample bodies for POST and PUT requests.

Add tests and fix failures

Example: “Add tests to every request in the Orders folder: check the status code, a response time under 500 ms, and one key field in the body.”

Claude Code adding tests to all five requests in the Orders folder, with the Create Order tests passing in Thunder Client — Tests added to every request in the Orders folder

Your assistant picks the right check for each request, and the tests appear in each request’s Tests tab, ready to edit. When something fails, it reads the real response and updates the request or your code:

After an API change: “We renamed customerId to accountId and made quantity required. Run the Orders folder, find every request and test that broke, and update them to match the routes in src/routes.”
When auth breaks: “Every request in the Payments collection now returns 401. Find out why and fix the auth setup, or tell me which variable to update.”

Run requests and collections

Example: “Run the Orders API collection and give me a report.”
Example: “Run the Regression collection 3 times, stop on the first failure, and save an HTML report.”

Your assistant shows the status, response and test results in the chat. Reports can be saved in HTML, JSON, XML, NUnit and CSV formats.

Claude Code running the Orders API collection: all 10 requests passed, with a results table and the Thunder Client summary report — All 10 requests pass, with a summary report in the chat

Available tools

Group	What it does	Tools
Inspect	See your setup, collections and environments	`debugInfo`, `listCollections`, `listEnvironments`, `getDetails`
Create	Add collections, folders and requests	`createCollection`, `createFolder`, `createRequest`
Update	Change requests and collection settings	`updateRequest`, `updateCollectionSettings`
Run	Send requests and run collections	`runRequest`, `runCollection`
Delete	Remove a request	`deleteRequest`

Feedback

The MCP server is open source under the MIT license on GitHub. We’d love to hear what you think of Thunder Client MCP Server v2. Try it out, and let us know on GitHub how we can make it better.