Skip to main content
Glama
MCP-Insomnia

MCP-Insomnia

by anggasct

Related Servers

Alternatives to MCP-Insomnia

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to import and export Postman collections, author and execute API requests, run collection tests with pm.* scripts, manage environments and request history, and inspect legacy Postman data through 23 structured tools.
      19 npm
      5
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create, run, and manage HTTP requests using the Invoker API client's .ivk format. It provides tools for scanning collections, executing requests, managing environments, and building documentation sites.
      9
      44 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to create, manage, and interact with Postman collections, workspaces, environments, and API requests directly from conversations.
      75 npm
      5
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to create, run, and save API requests and collections as local Gud API files, which are git-committable and viewable in VS Code-compatible editors.
      8
      55 npm
      -
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with Istek API Client for managing workspaces, collections, environments, variables, and request history. Allows natural language control of API development workflows including creating collections, adding requests, and managing environment configurations.
      -

    TDQS

    C2.9/5.0

    Scored across 30 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data