Onboarding request: io.wiremock/wiremock-cloud for GitHub MCP Registry

[ethangj]

Request

Please consider onboarding the official WireMock Cloud MCP server, io.wiremock/wiremock-cloud, into the GitHub MCP Registry.

The server is published and active in the Official MCP Registry. It is a first-party, remotely hosted MCP server maintained by WireMock Inc. that enables AI coding agents to build, validate, and manage API simulations in WireMock Cloud.

Server details

Field	Value
Official Registry name	io.wiremock/wiremock-cloud
Display name	WireMock Cloud
Current version	1.0.0
Registry status	Active / Latest
Provider	WireMock Inc.
Remote endpoint	https://mcp.wiremock.cloud/mcp
Transport	Streamable HTTP
Authentication	OAuth authorization-code flow with PKCE and dynamic client registration
Official integration repository	https://github.com/wiremock-inc/skills
Documentation	https://docs.wiremock.io/ai-mcp/agent-skills
Security policy	https://github.com/wiremock-inc/skills/security/policy
Support	https://www.wiremock.io/contact-now
Official Registry record	https://registry.modelcontextprotocol.io/v0.1/servers?search=io.wiremock%2Fwiremock-cloud

Capabilities

WireMock Cloud gives AI coding agents a controlled environment for developing and testing API-dependent software. Through MCP, agents can:

• Build complete API simulations from OpenAPI definitions or application requirements
• Create, import, validate, and modify WireMock stubs
• Convert simulations to stateful or data-driven behavior
• Author and debug dynamic response templates
• Configure realistic latency, faults, and failure conditions
• Search WireMock Cloud documentation while working
• Manage simulations without leaving the development workflow

Repository and client readiness

The public WireMock-owned repository includes:

• Installation and configuration instructions for GitHub Copilot and Visual Studio Code
• A GitHub Copilot plugin package and portable Agent Skills
• Remote and local MCP variants
• Security disclosure guidance
• Configuration examples for other MCP-compatible clients

The production endpoint is publicly reachable and advertises OAuth authorization metadata and protected-resource metadata. Unauthenticated MCP requests receive the appropriate OAuth challenge.

GitHub MCP Registry onboarding

Based on the process described in discussion #1257, initial inclusion in the GitHub MCP Registry remains manually curated, after which subsequent versions can synchronize from the Official MCP Registry.

Could the GitHub MCP Registry team please review and onboard io.wiremock/wiremock-cloud so it can become discoverable through github.com/mcp, the VS Code MCP gallery, and supported GitHub Copilot clients?

We are happy to provide reviewer access, test credentials, tool metadata, or any other information needed for evaluation.