Thunder Client MCP (official)
Score = points from 5 automated checks. Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs5/15
- License10/10
Tested npm thunderclient-mcp 2.0.2 (Thunder Client MCP Server v2, announced on the Thunder Client blog Nov 1, 2026; repo thunderclient/thunderclient-mcp; needs Node 22+). Its 12 tools listed without credentials. Real tool calls (no LLM, no credentials) ran without the VS Code extension installed: debugInfo, createCollection, listCollections and listEnvironments worked, using the bundled Thunder Client CLI 2.2.4 (data went to ~/.th-client in our sandbox home). runRequest, runCollection (send HTTP requests), update and delete tools were not called.
Tool-call test (2026-11-02, direct MCP stdio client, no LLM): pass. 4 of 4 calls passed: debugInfo, createCollection, listCollections (saw the new collection) and listEnvironments. No credentials; no HTTP requests were run. Evidence: local test run, Nov 2, 2026.
Transport (tested 2026-11-02): stdio
Score 90/100 · Tools 12 · Token cost ~8,602 · Compare · Last tested 2026-11-02 · Version tested 2.0.2 · Package thunderclient-mcp · Repo thunderclient/thunderclient-mcp
Summary: Thunder Client MCP (official) completed an MCP handshake without credentials and exposed 12 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 12
- Context cost
- 8,602 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 313 tokens; raw tools/list total 8,915. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key needed for the tools we called
- Tested
- 2026-11-02
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install thunderclient-mcp (Node 20, Linux) succeeded in 3s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 12 tools listed in 4.7s. |
| maintenance | pass | 25 | Repo pushed 3 days before test; 11 GitHub stars. |
| docs | partial | 5 | install instructions present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Schema context cost: ~8,602 tokens for 12 tools (37,437 bytes) · about 105% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-02
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 12 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-02 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
0104c760a6ed: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "thunderclient-mcp",
"version": "2.0.2",
"registry": "npm",
"status": "working",
"tested": "2026-11-02",
"tools_count": 12,
"tools_schema_tokens_est": 8602,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install thunderclient-mcp` (Node 20, Linux) succeeded in 3s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 12 tools listed in 4.7s."
],
"maintenance": [
"pass",
25,
"Repo pushed 3 days before test; 11 GitHub stars."
],
"docs": [
"partial",
5,
"install instructions present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y thunderclient-mcp
Tools listed
debugInfo, listCollections, getDetails, listEnvironments, createCollection, createFolder, createRequest, updateRequest, updateCollectionSettings, runRequest, runCollection, deleteRequest
Quick config
{
"mcpServers": {
"thunder-client-mcp": {
"command": "npx",
"args": [
"-y",
"thunderclient-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install thunderclient-mcp(Node 20). This is the exact command we ran on 2026-11-02. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (12 in our test).
{
"mcpServers": {
"thunder-client-mcp": {
"command": "npx",
"args": [
"-y",
"thunderclient-mcp"
]
}
}
}Test history
No dated events yet.
FAQ
Is Thunder Client MCP (official) deprecated?
No. thunderclient-mcp was not deprecated or archived when we last tested it on 2026-11-02.
What replaces Thunder Client MCP (official)?
Nothing; Thunder Client MCP (official) is not deprecated as of 2026-11-02.
Does Thunder Client MCP (official) need an API key?
No. It completed an MCP handshake with no credentials and listed 12 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.