What are the prerequisites to run Model Context Protocol Server?
You need Docker and Docker Compose installed on your system.
@eooo-io
Basic information
A Dockerized MCP server setup to deploy onto remote development servers
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
A containerized Model Context Protocol (MCP) server that enables communication between LLMs and tools through a standardized protocol. It provides both REST API and WebSocket interfaces for tool execution and context management, targeting developers building LLM-powered applications.
Deploy the server using Docker Compose: clone the repository, create tools, context, and data directories, configure a .env file, then run docker-compose up --build. Tools are placed as Python scripts in the tools directory, and the server exposes REST endpoints on port 3000 and a WebSocket at ws://localhost:3000 for real‑time communication.
You need Docker and Docker Compose installed on your system.
Place a Python script in the `tools` directory. The script should accept JSON parameters via `sys.argv[1]` and return JSON output printed to stdout.
Context files are stored as JSON in the `context` directory, each with a unique ID. They can be retrieved via the `GET /api/context/:id` REST endpoint or through WebSocket messages.
Run `docker-compose down` in the project directory.
Tool execution is isolated within the container, input validation is performed on all API endpoints, and context access can be restricted based on implementation needs.

Build and run websites, APIs, automations, and admin tools from chat. Your agent creates the data, logic, pages, and scheduled jobs; Tessryx hosts them on your own domain. No code generated, nothing to deploy.
The official Webshare MCP server. Manage your proxies, usage, plans and billing from Claude, Cursor or any MCP client. Sign in with OAuth, no API key.
MCP server connecting to Kubernetes
Development environments for coding agents. Enable multiple agents to work safely and independently with your preferred stack.
Official OutageDeck MCP server for vendor-published cloud and SaaS status, incident timelines, and observed uptime history.
Comments