Bring Route Optimization
to Claude Desktop
Learn how to connect Upper Route Planner to Claude Desktop and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Upper Route Planner MCP Server?
Connect your Upper Route Planner account to any AI agent and take full control of your delivery logistics and high-fidelity route orchestration through natural conversation.
What you can do
- Route Portfolio Orchestration — List all optimized delivery routes, retrieve detailed high-fidelity status metadata, and monitor route duration programmatically
- Stop & Task Intelligence — Access your complete directory of high-fidelity route stops and tasks to stay on top of field delivery progress in real-time
- Logistics Provisioning — Programmatically generate new high-fidelity delivery tasks with precise time windows and customer metadata directly through your agent
- Driver Monitoring Architecture — Access high-fidelity driver assignments and resource allocation details to understand and orchestrate your field workforce
- Stop Detail Discovery — Access complete high-fidelity metadata for specific delivery stops to maintain perfect contextual alignment for every parcel
- Operational Monitoring — Verify account-level API connectivity and monitor route orchestration volume directly through your agent for perfectly coordinated service scaling
How it works
1. Subscribe to this server
2. Retrieve your API Token from your Upper dashboard (Settings > Web Service API)
3. Start managing your delivery growth from Claude, Cursor, or any MCP client
No more manual route checking or missing stop updates. Your AI acts as your dedicated logistics coordinator and route architect.
Who is this for?
- Logistics Managers — instantly retrieve route statuses and monitor driver progress using natural language commands without leaving your creative workspace
- Operations Leads — verify high-fidelity delivery metadata and manage task priority to ensure healthy field operations
- Dispatchers — analyze technical route efficiency and monitor task volume through simple AI queries
Built-in capabilities (6)
Check API Status
Add a delivery task
Get specific route stop
Get stop details
List delivery drivers
List delivery routes
Why Claude Desktop?
Claude Desktop is the definitive way to connect Upper Route Planner to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Upper Route Planner in Claude Desktop
Upper Route Planner and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Upper Route Planner to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Upper Route Planner in Claude Desktop
The Upper Route Planner MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Upper Route Planner for Claude Desktop
Every tool call from Claude Desktop to the Upper Route Planner MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Upper API Token?
Log in to your account, navigate to Settings > Web Service API, and copy your unique high-fidelity API Token.
Can I check specific stop details via AI?
Yes! The get_upper_stop_details tool allows your agent to retrieve high-fidelity metadata including service time, customer contact, and delivery notes.
How do I list my optimized routes?
Use the list_upper_routes tool to retrieve the complete high-fidelity directory of routes along with their assigned drivers and status.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.