Bring Railway Management
to Cursor
Learn how to connect Cedar AI to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Cedar AI MCP Server?
Connect your Cedar AI railway management account to any AI agent and simplify how you coordinate rail operations, track car movements, and manage logistics documentation through natural conversation.
What you can do
- Inventory Management — List all railcars currently in your facility and retrieve detailed metadata and status for individual units.
- Car Movement Tracking — Record placements (setouts) and removals (pickups) of railcars at specific locations or tracks.
- Logistics Documentation — List and query waybills to understand shipping instructions, routes, and commodity data.
- Work Order Control — Manage the lifecycle of movement instructions by listing and updating work orders and associated tasks.
- Consist Coordination — Record train arrivals and departures to keep your inventory and operations synchronized.
- Status Maintenance — Update railcar tags and conditions (e.g., Bad Order, Empty/Loaded) directly via AI commands.
How it works
1. Subscribe to this server
2. Enter your Cedar AI API Key (found in your developer settings)
3. Start managing your railway ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Railroad Operators & Terminal Managers — quickly check yard inventory and record car movements via simple AI queries.
- Logistics Coordinators — monitor waybills and manage work orders across different tracks directly from the workspace.
- Fleet Managers — track railcar statuses and conditions to optimize equipment availability via the AI assistant.
Built-in capabilities (12)
Record train arrival
Record train departure
Get details for a specific railcar
Get details for a specific waybill
Get details for a specific work order
List railcars currently in inventory
List waybills
List work orders
Record removal of cars
Record placement of cars
g., Bad Order, Clean, Loaded/Empty). Update status of a railcar
Update a work order
Why Cursor?
Cursor's Agent mode turns Cedar AI into an in-editor superpower. Ask Cursor to generate code using live data from Cedar AI and it fetches, processes, and writes. all in a single agentic loop. 12 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
Cedar AI in Cursor
Cedar AI and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Cedar AI 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 Cedar AI in Cursor
The Cedar AI 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 12 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
Cedar AI for Cursor
Every tool call from Cursor to the Cedar AI MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I record a railcar movement via AI?
Yes! Use the setout_cars tool to record placement or pickup_cars for removal. Provide the location name and a list of railcar IDs to log the movement instantly.
How do I see the latest waybills for my shipments?
Run the list_waybills query. The agent will retrieve a history of active and completed shipping instructions, including route details and commodity info.
Is it possible to check the status of a specific work order via AI?
Absolutely. Use the get_work_order_details tool with the Work Order ID to retrieve the current status, assigned tasks, and completion progress.
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.