Skip to main content
Glama
doossee

Invoker MCP Server

by doossee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Invoker MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP-Insomnia

      anggasct
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to create, manage, and execute API collections, requests, and environments in Insomnia-compatible formats. It supports direct synchronization with the local Insomnia app database and importing from OpenAPI, Postman, and cURL.
      30
      31 npm
      26
      MIT

    • Swagger/Postman MCP Server

      MCP-Mirror
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to dynamically discover and interact with APIs through Swagger/OpenAPI specifications and Postman collections using a strategic four-tool approach. It streamlines API integration by providing universal tools for endpoint discovery, detailed request information, and authenticated execution.
      1
      -

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

    • API Debugger MCP

      MahaR54
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect, test, validate, compare, and debug HTTP APIs through a structured toolkit, with features such as secret redaction, response contract validation, regression comparison, health checks, and incident investigation workflows.
      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

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: creating environments, building sites, creating/reading/sending requests, listing collections/environments, and managing variables. The descriptions clearly differentiate their functions, preventing misselection.

    Naming Consistency5/5

    All tools follow a consistent 'invoker_verb_noun' pattern (e.g., invoker_add_environment, invoker_build_site). This predictable naming makes it easy for agents to understand and navigate the toolset without confusion.

    Tool Count5/5

    With 9 tools, the server is well-scoped for managing Invoker collections, environments, and requests. Each tool serves a specific role in the workflow, from setup to execution, without being overly sparse or bloated.

    Completeness4/5

    The toolset covers core CRUD and lifecycle operations for environments, variables, and requests, with good workflow support. A minor gap exists in lacking tools for deleting or updating environments/requests, but agents can work around this with file system operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources