MCP-Insomnia
Server 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 |
|---|---|
| create_collectionB | Create a new collection/workspace in Insomnia |
| list_collectionsB | List all collections and their structure |
| get_collection_detailC | Get full details and statistics of a specific collection |
| export_collectionB | Export collection to JSON (Insomnia V4 format) |
| create_folderA | Create a folder to group requests within a collection |
| list_requestsB | List all requests across collections. Optionally filter by collectionId. |
| get_requestC | Get full details of a specific request by ID |
| get_request_historyB | Get the execution history of a specific request |
| create_request_in_collectionB | Create a new request within a specific collection/folder |
| update_requestC | Update an existing request |
| delete_requestA | Delete a request from a collection |
| execute_requestC | Execute a request and get a response |
| set_environment_variableC | Set environment variables for a collection |
| get_environment_variablesB | Get environment variables from a collection |
| import_from_insomnia_exportB | Import collections from a standard Insomnia V4 export file |
| generate_code_snippetB | Generate a code snippet for a request in various languages/frameworks |
| import_from_curlB | Create a request from a cURL command |
| import_from_postmanA | Import collections from a Postman Collection v2.1 JSON file |
| import_from_openapiB | Generate requests from OpenAPI/Swagger specification |
| list_insomnia_collectionsB | List all collections directly from Insomnia app (requires Insomnia to be installed) |
| list_insomnia_projectsB | List all projects from Insomnia app |
| get_insomnia_collectionB | Get a complete collection from Insomnia app by workspace ID |
| sync_from_insomniaC | Import a collection from Insomnia app into MCP storage |
| sync_to_insomniaC | Export a collection from MCP storage to Insomnia app |
| preview_sync_to_insomniaA | Preview the effect of syncing a collection to Insomnia: classify documents into toCreate/toUpdate/toDelete vs the Insomnia target. Performs no writes. |
| sync_all_from_insomniaB | Import all collections from Insomnia app into MCP storage |
| get_insomnia_requestC | Get detailed request information directly from Insomnia |
| execute_insomnia_requestA | Execute a request directly from Insomnia app without syncing. Supports environment variable substitution. |
| searchB | Search for a keyword across all collections, folders, and requests |
| get_statsB | Get global statistics of all collections |
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 30 tools
Several tools form near-identical pairs differentiated mainly by source: MCP storage vs. live Insomnia app (e.g., list_collections vs. list_insomnia_collections, get_request vs. get_insomnia_request, execute_request vs. execute_insomnia_request). The descriptions clarify the distinction, but an agent must read carefully to avoid picking the wrong variant.
The set mostly follows a clear verb_noun snake_case pattern: create_collection, list_requests, update_request, delete_request. The main inconsistency is where 'insomnia' appears in names (list_insomnia_collections vs. sync_from_insomnia), but the overall convention remains predictable.
With 30 tools, the server feels over-sized even for a feature-rich Insomnia integration. Many operations are duplicated across MCP storage and live-app variants, inflating the surface area without adding proportional capability.
Requests have solid lifecycle coverage with create, get, update, delete, execute, and search, and imports/exports are broad. However, collections lack update and delete operations, and folders have no update/delete path, leaving notable CRUD gaps in the core domain.