Skip to main content
Glama
Erivelto47

wiremock-mcp

by Erivelto47
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to wiremock-mcp

No user-submitted related servers found.

    Related Servers

    • mockserver-mcp

      Akkshay10
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for interacting with MockServer, enabling AI assistants to create mock HTTP expectations, verify requests, clear state, and manage MockServer instances programmatically.
      6
      43 npm
      1
      MIT
    • @restforge-dev/mcp-server by restforge

      @restforge-dev/mcp-serverofficial

      restforge
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes RESTForge capabilities to AI agents, enabling them to set up, configure, generate code, and manage RESTForge projects through natural language.
      29
      44 npm
      MIT

    • forge-mcp

      amigo-ai
      A
      license
      C
      quality
      B
      maintenance
      Prototype MCP server enabling coding agents to manage Amigo Agent Forge operations, including org credentials, entity configurations, conversation simulations, and version sets.
      37
      33 npm
      ISC

    • Mock MCP Server

      DiscreteTom
      A
      license
      B
      quality
      D
      maintenance
      A mock MCP server for testing MCP client implementations and development workflows. Supports tools, prompts, and resources across multiple transport protocols (stdio, HTTP, SSE).
      1
      MIT

    • agent-regress

      Gaurav7974
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that provides tools for AI coding agents to execute, evaluate, and diff regression tests for LLM agents.
      1 npm
      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

    A3.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinctly different purpose: status, mock CRUD, and request journal operations. There is no ambiguity between listing, getting, creating, updating, deleting mocks, or between request list/get/unmatched/count/clear.

    Naming Consistency4/5

    Most tools follow a clear resource_action pattern (mock_list, request_get, etc.). The only deviation is wiremock_status, which uses a noun phrase instead of an action verb, but it is still understandable and consistent with the resource-based naming.

    Tool Count5/5

    12 tools is well-scoped for a WireMock admin server, covering status, mock lifecycle management, and request journal operations without excessive overlap or unnecessary additions.

    Completeness4/5

    The tool surface provides full CRUD for stub mappings and a robust set of request journal operations. Minor gaps exist (e.g., no tool for managing global settings or scenarios), but the core WireMock workflows are effectively covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources