About MCP Server
An initial server skeleton for the Multi-Agent Code Planner. The README documents endpoints for executing planning commands and checking service health.
Key features
- 01Planning command execution endpoint
- 02Health-check endpoint
Use cases
- 01Check whether the service is running
- 02Submit a planning command
MCP support
The project is described as an MCP server, but the README only documents HTTP endpoints for health checks and planning-command execution, not MCP tools or resources.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP Server
Initial skeleton for the Multi-Agent Code Planner (MCP) server.
Prerequisites
- Node.js v14+ / npm
- Docker & Docker Compose
Setup
- Copy `.env.example` to `.env` and set values.
- Build & run locally: ```bash npm install npm start ```
- Or with Docker Compose: ```bash docker-compose up --build -d ```
- Verify health: ```bash curl http://localhost:8205/health ```
Endpoints
- `GET /health` — Health check
- `POST /execute` — Execute planning command
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.