Syncnox MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Syncnox MCP Serveroptimize route R100 for shortest distance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Syncnox MCP Server
An MCP server that gives AI agents (like Claude) direct access to the Syncnox route-management backend.
Transport
Streamable HTTP — the server exposes a single HTTP endpoint at /mcp.
This means you can deploy it in Docker, expose it over the network, and connect multiple remote clients.
Related MCP server: Logistics AI MCP
Authentication
Every request must include the header:
X-API-Key: <your MCP_API_KEY>The server itself also authenticates to your Syncnox FastAPI backend using a Bearer token (API_KEY).
Available Tools
Tool | What it does |
| Add a new stop to an existing route |
| Re-order stops for fastest time or shortest distance |
| Get ETA for the whole route or a single stop |
| Fetch full route details including all stops |
| Fetch the details of a specific job by its ID |
| Add a single job (address geocoded automatically) |
| Add multiple jobs from a JSON list of dictionaries (addresses geocoded automatically) |
| Import jobs from CSV content passed directly as text |
| Import a list of jobs from a local CSV/Excel file path |
Project Layout
syncnox-mcp/
├── server.py ← entry point, Streamable HTTP app
├── middleware.py ← API-key auth middleware (production ASGI wrapper)
├── config.py ← settings loaded from .env
├── api_client.py ← shared httpx client for Syncnox backend
├── tools/
│ ├── __init__.py ← central tools registry exposing register_all()
│ ├── routes.py ← route-related tools (get_route, optimize_route, get_eta)
│ ├── stops.py ← stop-related tools (add_stop)
│ └── jobs.py ← job-related tools (get_job_info)
├── requirements.txt
└── .env ← secrets (not committed to git)Setup
# 1. Create & activate virtual env
python -m venv .venv
source .venv/bin/activate
# 2. Install dependencies
pip install -r requirements.txt
# 3. Configure
cp .env .env.local # edit values
# Set: API_BASE_URL, API_KEY, MCP_API_KEY, PORT
# 4. Run
python server.pyServer starts at http://0.0.0.0:8100.
Connecting a Client
In Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"syncnox": {
"type": "http",
"url": "http://localhost:8100/mcp",
"headers": {
"X-API-Key": "changeme-mcp-secret"
}
}
}
}Health Check
curl http://localhost:8100/health
# → OKDeployment on EC2
cd syncnox-mcp
git pull
sudo systemctl restart syncnox-mcp.serviceThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mav92121/syncnox-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server