thunderclient-mcp
OfficialREADME.md
<p align="center">
<img src="https://github.com/thunderclient/thunder-client-support/blob/21d62c97dcc8168dc678b165fe678fd12c2f476b/images/thunder-icon.png" width="120" height="120" />
</p>
# Thunder Client MCP Server
The Thunder Client MCP server is **open source** and lets your AI assistant create, update, and run Thunder Client requests and collections from plain-language prompts.
Compatible with **Claude Code**, **Codex**, **GitHub Copilot**, **Cursor**, **Windsurf**, and any MCP-compatible AI tool.
## Documentation
For requirements, installation, and setup instructions, see the [Thunder Client MCP documentation](https://docs.thunderclient.com/mcp).
---
## Contributing
Issues and pull requests are welcome.
To build the server locally, run:
```bash
git clone https://github.com/thunderclient/thunderclient-mcp
cd thunderclient-mcp
npm install
npm run build
```
Then, in your MCP configuration, replace `npx -y thunderclient-mcp` with `node /path/to/thunderclient-mcp/dist/index.js`.
## License
This project is open source and licensed under the [MIT License](LICENSE).
TDQS
B3.2/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: one creates API endpoints and handles collection/folder creation, the other runs a debug command. No overlap or ambiguity.
Naming Consistency5/5
Both tools follow a consistent 'tc_verb' naming pattern with clear verbs ('create' and 'debug'), making it predictable for an agent.
Tool Count2/5
Only 2 tools for a server managing API endpoints is very limited. A typical CRUD surface would require at least 5-8 tools (list, get, create, update, delete, debug, etc.).
Completeness2/5
The tool surface covers only creation and debugging. Critical operations like listing, updating, deleting endpoints or managing collections/folders are missing, leaving significant gaps for common workflows.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues