Bring Railway Management
to Claude Desktop
Learn how to connect Cedar AI to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Cedar AI to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 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
Cedar AI in Claude Desktop
Cedar AI and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Cedar AI 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 Cedar AI in Claude Desktop
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 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
Cedar AI for Claude Desktop
Every tool call from Claude Desktop 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.
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.