myshoes-mcp-server
@whywaita
The myshoes MCP Server is Model Context Protocol (MCP) compliant server for the whywaita/myshoes.
Overview
What is myshoes-mcp-server?
myshoes-mcp-server is a Model Context Protocol (MCP) compliant server that implements a JSON-RPC server for managing target data from the myshoes system. It is intended for users who want to integrate myshoes with MCP-capable clients, such as VS Code.
How to use myshoes-mcp-server?
Install it using Docker and configure it in your MCP client (e.g., VS Code). The server runs via stdio and requires a --host argument pointing to the myshoes instance (e.g., http://192.0.2.10:8080). An example configuration for VS Code is provided in the README.
Key features of myshoes-mcp-server
- JSON-RPC based MCP server for myshoes
- Manages target data from the myshoes platform
- Runs via Docker with stdio transport
- Configured with a
--hostargument for the myshoes instance - Early development stage, not production ready
Use cases of myshoes-mcp-server
- Integrating myshoes target data management with MCP clients
- Automating target data operations in myshoes deployments
- Building MCP-based tools that interact with myshoes
FAQ from myshoes-mcp-server
What transport does myshoes-mcp-server use?
It uses the stdio transport, as shown in the VS Code MCP configuration.
How do I install myshoes-mcp-server?
You run the Docker image ghcr.io/whywaita/myshoes-mcp-server:latest with the appropriate arguments, including the --host flag.
Is myshoes-mcp-server ready for production?
No, the project is in early development and not yet ready for production use.
What does the --host parameter do?
It specifies the URL of the myshoes server instance that the MCP server will communicate with.
Can I use myshoes-mcp-server without Docker?
The README only provides a Docker-based installation method; no alternative installation is described.
