thunderclient-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tc_createB | Create API endpoints to Thunder Client, automatically creating collections and folders if they do not already exist. |
| tc_debugB | Runs the Thunder Client debug command and display the result. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
Both tools follow a consistent 'tc_verb' naming pattern with clear verbs ('create' and 'debug'), making it predictable for an agent.
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.).
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.