START_MCP_SERVER.md•3.15 kB
# Start Standalone MCP Server
## Why Standalone?
The MCP server runs **completely independently** from your main solid-backend system to ensure:
- ✅ High traffic (10K merchants) won't impact your backend
- ✅ Separate resource allocation (2 CPU cores, 2GB RAM)
- ✅ Can be restarted without touching solid-backend
- ✅ Monitored via admin dashboard at http://localhost:8080/admin/mcp-server
## Start the MCP Server
```bash
cd /Users/adamcampbell/Desktop/Solid/solid-mcp-server
docker-compose up -d
```
## Check Status
```bash
docker ps | grep solid-mcp-server
docker logs solid-mcp-server
```
## Access Points
- **Health Check**: http://localhost:8092/health
- **Admin Dashboard**: http://localhost:8080/admin/mcp-server
- **API Stats**: http://localhost:8092/api/stats
- **List Tools**: http://localhost:8092/api/tools
## Stop the MCP Server
```bash
cd /Users/adamcampbell/Desktop/Solid/solid-mcp-server
docker-compose down
```
## Resource Allocation
The MCP server has dedicated resources:
- **CPU Limit**: 2.0 cores
- **Memory Limit**: 2GB
- **Reserved CPU**: 0.5 cores minimum
- **Reserved Memory**: 512MB minimum
This ensures the MCP server can handle high traffic without starving your main backend services.
## Architecture
```
┌─────────────────────────────────────────┐
│ Your Main System (solid-backend) │
│ - solid-backend (port 8090) │
│ - solid-postgres (port 5432) │
│ - solid-redis (port 6379) │
│ Network: solid-network │
└─────────────────────────────────────────┘
↓ HTTP Calls
┌─────────────────────────────────────────┐
│ Standalone MCP Server │
│ - solid-mcp-server (port 8092) │
│ - 608 tools │
│ - 36 categories │
│ Network: bridge (default) │
│ Resource: 2 CPU, 2GB RAM │
└─────────────────────────────────────────┘
↓ Monitored by
┌─────────────────────────────────────────┐
│ Admin Dashboard │
│ http://localhost:8080/admin/mcp-server │
└─────────────────────────────────────────┘
```
## Important Notes
1. **Do NOT add this to solid-backend/docker-compose.yml**
2. **Start it separately** using its own docker-compose.yml
3. **Uses host.docker.internal** to call your backend without being on the same network
4. **Shows up in Docker Desktop** as `solid-mcp-server`
5. **Managed from admin dashboard** for monitoring only
This isolation ensures your main system stays stable even under heavy MCP traffic.