Skip to main content
Glama
Sign In
Thunder Client License Manager MCP Server

Thunder Client License Manager MCP Server

by chezsmithy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Thunder Client License Manager MCP Server

No user-submitted related servers found.

    Related Servers

    • thunderclient-mcp

      thunderclient-mcpofficial

      thunderclient
      A
      license
      B
      quality
      B
      maintenance
      Enables AI tools to create and manage API requests and collections in Thunder Client, with automated collection and folder creation.
      2
      163 npm
      11
      MIT

    • Linear MCP Server

      timottowitz
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Linear's API to manage issues, projects, and teams. Supports creating, updating, searching, and deleting issues, along with project management and team operations through API key authentication.
      13
      672 npm
      MIT

    • Istek MCP Server

      istekapp
      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.
      -

    • Bruno MCP Server

      jcr82
      A
      license
      A
      quality
      D
      maintenance
      Integrates Bruno CLI for API testing, enabling users to run API requests and collections, manage environments, generate test reports (JSON/JUnit/HTML), and validate collection structures through natural language commands.
      9
      39 npm
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add, get, and remove licenses. The actions (add, get, remove) are mutually exclusive and target the same resource (licenses), leaving no room for confusion or overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with the prefix 'thunderclient_' and use clear action verbs (add, get, remove) followed by the noun 'license'. There are no deviations in style or convention.

    Tool Count4/5

    Three tools are appropriate for a license manager, covering core CRUD operations (add, get, remove). It is slightly under-scoped as it lacks an update tool, but the count is reasonable for the domain.

    Completeness4/5

    The tool set covers the essential lifecycle of license management: create (add), read (get), and delete (remove). A minor gap exists with no update tool for modifying existing licenses, but agents can work around this by removing and re-adding.

    Resources