thunderclient

The Thunder Client MCP Server enables AI-assisted generation and management of Thunder Client API requests and collections. It exposes tools such as tc_create, which saves endpoints into Thunder Client by automatically creating folders and collections as needed, and tc_debug, which runs Thunder Client in debug mode to surface CLI details for troubleshooting. You can integrate these tools with AI environments like Cline, Continue.dev, or GitHub Copilot to automatically extract API endpoints from codebases, generate requests, and organize them within Thunder Client workspaces. Use tc_create to derive API requests from your project and place them into a structured Thunder Client collection, and use tc_debug to diagnose issues in your Thunder Client setup or the generated requests.

To use the MCP server, configure it in your environment according to your platform (Cline, Continue.dev, or Copilot) to point at the Thunder Client MCP Server using the npx thunderclient-mcp invocation. Once configured, you can issue prompts that instruct the tool to create or update API requests in Thunder Client, and the MCP server will execute the corresponding Thunder Client CLI operations behind the scenes.

Prerequisites:

• Node.js installed on your machine (recommended LTS version).
• Optional: npm or pnpm for package management.
• Access to Thunder Client (Business/Enterprise plan) if required by features.

Installation steps:

1. Install the MCP server package (via your project or global environment):
   • You can install locally in your project or rely on npx to fetch it on demand:
     • Using npm: npm install thunderclient-mcp
     • Or simply rely on npx without installing: npx -y thunderclient-mcp
2. Build or prepare the MCP server if needed by your environment. The Thunder Client MCP Server expects a dist/index.js artifact when running in local Dev mode, so if you build locally, ensure the path to index.js is accessible to your MCP host.
3. Configure your MCP host (Cline, Continue.dev, or Copilot) to point at the MCP server using the provided command:
   • Command: npx
   • Args: -y thunderclient-mcp
   • If you build locally, replace thunderclient-mcp with the path to your local dist/index.js (e.g., /path/to/thunder-mcp/dist/index.js).
4. Verify installation by running a simple prompt to create a Thunder Client API request and ensure it appears in Thunder Client.

Notes:

• If you run in a local Dev mode setup, ensure the index.js path is correct and accessible by your MCP host.
• The Thunder Client MCP server requires a valid Thunder Client subscription to use certain features as documented.

Tips and common issues:

• Ensure you are using the correct MCP environment: Cline (stdio), Continue.dev (YAML), or Copilot (Agent mode) and configure the command as npx thunderclient-mcp for standard usage. If you are in a local Dev setup, point to the built index.js in the dist folder.
• When using paths, prefer absolute paths to avoid runtime path issues across environments.
• If the MCP server cannot find Thunder Client workspaces, double-check projectDir and workspace configuration in Thunder Client and ensure the MCP has permission to read/write those directories.
• The available tools tc_create and tc_debug assume Thunder Client CLI is installed and accessible in the environment where the MCP server runs.
• For production usage, ensure you are compliant with Thunder Client’s business/enterprise terms and have the necessary API access for creating and managing collections.