Bring Route Optimization
to Cursor
Learn how to connect Upper Route Planner to Cursor 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 Cursor?
Cursor's Agent mode turns Upper Route Planner into an in-editor superpower. Ask Cursor to generate code using live data from Upper Route Planner and it fetches, processes, and writes. all in a single agentic loop. 6 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Upper Route Planner in Cursor
Upper Route Planner and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Upper Route Planner to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.