metersphere
MCP server from metersphere/metersphere-mcp-server
claude mcp add --transport stdio metersphere-metersphere-mcp-server docker run -i --rm -p 8000:8000 -e accessKey=${env:accessKey} -e signature=${env:signature} -e meterSphereUrl=${env:meterSphereUrl} metersphere-mcp-server \
--env accessKey="your-access-key" \
--env signature="your-signature" \
--env meterSphereUrl="http://your-metersphere-url"How to use
MeterSphere MCP Server exposes testing and documentation tooling via the MCP interface so LLMs and IDE plugins can interact with MeterSphere for API testing, interface documentation, mock service creation, and compatibility checks. Clients connect over HTTP+SSE, STDIO, or Docker channels to issue commands such as running tests, fetching API definitions, generating test assets, and validating compatibility between services and definitions. Useful scenarios include invoking test suites from natural language prompts, retrieving interface schemas, spinning up mock endpoints, and extracting documentation from API definitions for quick reference. The server is designed to be a bridge between development tools and the MeterSphere testing ecosystem, enabling left-shifted testing and automated workflows inside editors, assistants, or chat interfaces.
How to install
Prerequisites:
- Docker installed and running (for the provided run command)
- Optional: MeterSphere instance accessible at MeterSphereURL if using remote resources
Install steps:
- Clone the repository: git clone https://github.com/metersphere/metersphere-mcp-server.git
- Build the MCP server image (if you want to run a local image): docker build -t metersphere-mcp-server .
- Run the server via Docker (as shown in the example):
docker run -i --rm -p 8000:8000
-e accessKey=your-access-key
-e signature=your-signature
-e meterSphereUrl=http://your-metersphere-url
metersphere-mcp-server - Alternative: if you prefer a non-Docker rollout, ensure Java/Maven is installed and run the server according to the project’s build output (not shown in this README).
Additional notes
Environment variables and authentication:
- AK/SK style credentials (accessKey and signature) are supported for authenticating MCP requests.
- MeterSphere URL should point to your MeterSphere deployment when needed.
- The default HTTP port is 8000; adjust via deployment or environment as required. Common issues:
- If the server fails to start on port 8000, ensure no other process is occupying the port and Docker permissions are correct.
- When using Docker, ensure the image name matches metersphere-mcp-server and that environment variables are properly propagated to the container.
- For SSE connections, verify baseUrl and path configurations in the client settings correspond to your server’s exposed endpoints.
