Cedar AI MCP for AI. Manage Rail Yard Movements in Natural Conversation
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Cedar AI manages your entire rail logistics operation through conversation. This MCP connects directly to your railway management account, letting you track car movements, check waybill data, and manage work orders just by talking to your agent.
Need to know where a train is? Want to update a car's status? You get the answer instantly without logging into five different dashboards.
What your AI can do
Arrive train
Logs when an entire train enters the terminal facility.
Depart train
Logs when a train leaves the terminal facility.
Get railcar details
Pulls specific metadata and status for one railcar you name.
List every railcar currently on site and pull up detailed information for any specific unit.
Record when cars are placed (setout) or removed (pickup) from a specific yard location or track.
List and check the details of waybills to understand shipment routes, commodities, and instructions.
View and update work orders, tracking tasks associated with a specific movement instruction.
Record when an entire train enters or leaves the facility to keep your overall system count accurate.
Ask an AI about this
Waiting for input…
Cedar AI with 12 Tools
Use these twelve tools to log everything from car placements and train arrivals to detailed shipment lookups and asset condition updates.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Cedar AI on VinkiusArrive Train
Logs when an entire train enters the terminal facility.
Depart Train
Logs when a train leaves the terminal facility.
Get Railcar Details
Pulls specific metadata and status for one railcar you name.
Get Waybill Details
Retrieves the full shipment details, including origin and destination, for a...
Get Work Order Details
Shows all information related to one work order ID, including tasks and history.
List Inventory
Presents a full list of every railcar currently registered in the yard.
List Waybills
Lists all available waybill numbers for review.
List Work Orders
Displays a list of active and completed work orders.
Pickup Cars
Records the removal of cars from their current location in the yard.
Setout Cars
Logs the placement of a group of cars into a specific track or customer spot.
Update Railcar Status
Changes the official condition tag (like 'Bad Order' or 'Loaded') for a railcar unit.
Update Work Order
Modifies the details or status of an existing work order.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Cedar AI, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cedar AI. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking rail yard movements used to mean too many clicks.
Today, if a car needs to move from the main track to a customer spot, you gotta jump between four different applications. You check inventory in one tab, log the movement in another system's form, then update the work order status manually, and finally notify someone via email just so they know it's done. It’s slow, and someone always forgets a step.
With this MCP, you tell your agent what needs to happen—for instance, 'Move TBOX 101 from Track A to Customer Spot B.' The system handles the sequence: it checks inventory first, executes the `setout_cars` record, and updates the work order status all in one go. You just get a confirmation that it's done.
Cedar AI MCP gives you real-time visibility into asset conditions.
Before this, if an employee found damage on a car, they had to find the physical log sheet, write down the car number and condition code (Bad Order, Empty/Loaded), then manually call maintenance. That data sat in a silo until someone transcribed it.
Now, you just tell your agent: 'Update status for TBOX 102 to Bad Order.' The system runs `update_railcar_status` instantly. You don't wait; the record changes right when you say it.
What your AI can actually do with this
Coordinating rail operations used to mean juggling multiple screens: checking inventory in one tab, looking up shipping details in another, and then emailing a separate request just to change a work order status. Now, you can handle it all through natural conversation. You simply ask your agent what you need—like 'What cars are waiting at Track 3?' or 'Show me the next steps for waybill WB-88231.' The system pulls that data right from Cedar AI and gives you a clear answer.
Whether you're using Claude, Cursor, or any other MCP-compatible client, your agent handles the complexity in the background. Connecting to this service via Vinkius means you get immediate access to all of these core functions without needing complex middleware. You manage everything from logging train arrivals to updating asset conditions—all while staying in your familiar chat interface.
019dd0ca-5d68-7349-a0c5-5d9a0f0cb2de Here's how it actually works
The bottom line is, your agent translates complex rail commands into simple chat requests.
First, subscribe to this MCP and enter your Cedar AI API Key in the Vinkius platform.
Your agent connects using that key. You then tell it what you need—for example, 'List all cars at the main yard.'
The system executes the necessary tool calls and returns a plain language summary of the data (e.g., 'You have 15 units: X is loaded, Y is empty').
Who is this actually for?
Terminal managers and ops coordinators who are tired of jumping between asset tracking software, logistics databases, and work order systems just to get a status update. This tool is for the people who need real-time visibility without logging into five different dashboards.
Checking yard inventory via list_inventory or recording train arrivals using arrive_train to ensure the system count matches physical reality.
Monitoring shipments by listing waybills (list_waybills) and managing associated work orders across different tracks.
Tracking the condition of assets using update_railcar_status to keep track of equipment availability and maintenance status.
What Changes When You Connect
Instead of opening the inventory module and manually searching, you just ask your agent to list_inventory for everything. You get a real-time snapshot immediately.
When cars move, don't rely on manual logging. Just tell your agent to execute setout_cars or pickup_cars, and it updates the yard status automatically.
Need context on a shipment? Don't guess. Use get_waybill_details to pull up everything about that waybill, including its full route history.
Managing work orders is easier than clicking through forms. Simply ask your agent to view details with get_work_order_details, and you know exactly what needs doing next.
Keep your physical count matching the books. Use arrive_train or depart_train whenever a train crosses your yard limits, guaranteeing system accuracy.
See it in action
The Yard Inventory Check
A manager needs to know how many empty cars are available for loading. Instead of running a report and cross-referencing sheets, they prompt their agent: 'List all railcars and filter by Empty.' The agent runs list_inventory and gives the precise count in seconds.
Completing a Shipment
A coordinator finishes loading cars for a customer. They tell the agent to execute setout_cars, specifying the car numbers and track location. The system logs the placement, updating both the inventory records and associated work orders.
Handling an Exception
A loaded railcar arrives but has damage. Instead of going to a tablet terminal, the ops staff tells their agent: 'Update status for BNSF 98765 to Bad Order.' The system runs update_railcar_status immediately.
Investigating Shipment Issues
A team member finds a discrepancy in paperwork. They ask the agent to review waybill WB-231 and then follow up with 'Show me the car details for TBOX 456.' The agent runs get_waybill_details and then get_railcar_details sequentially.
The honest tradeoffs
Assuming Status
A user assumes a car is empty just because it's sitting in the yard. They try to proceed with work based on that assumption.
Always verify the condition first. Use get_railcar_details or check the output of list_inventory before making any moves or assuming status.
Manual Tracking
A train arrives, and staff manually update a spreadsheet log hours later, leading to data gaps.
Use the agent to record the event immediately. Prompt for arrive_train right when the train crosses the threshold. It logs it instantly.
Confusing Tools
A user tries to update a work order status but forgets which tool is responsible, resulting in an incomplete task log.
If you need to change the job's status, use update_work_order. If you are just moving physical cars, use setout_cars or pickup_cars.
When It Fits, When It Doesn't
Use this MCP if your work involves tracking state changes across multiple related systems—specifically when a car's location, its condition, and its associated paperwork all need to move together. If you only need to read simple static data (e.g., 'What is the name of the yard?'), use a basic database query tool instead. Don't try to manage inventory just by calling list_waybills; that only shows papers, not physical assets. For managing movement, always follow up a list command like list_inventory with an action command like setout_cars to make sure your state changes are logged correctly.
Questions you might have
How do I check a car's status with get_railcar_details? +
You give the agent the railcar number. It pulls all metadata for that specific unit, including its current condition and location history. This is useful if you only know the car ID but not where it is.
Can I use list_inventory to see everything? +
Yes, list_inventory gives you a full roster of every railcar currently in your yard. You can then ask follow-up questions about specific units found in that list.
Does setout_cars update the work orders? +
Yes, logging the placement of cars with setout_cars updates both the physical inventory record and helps keep associated work order tasks synchronized with the actual movement.
What is the difference between list_waybills and get_waybill_details? +
list_waybills just gives you a rundown of all waybill numbers available. You must use get_waybill_details to pull up the actual content, like shipping routes or commodities.
What credentials do I need before running `list_inventory`? +
You must provide a valid Cedar AI API key. This MCP authenticates using that key to connect to your specific railway management account. Don't worry about refreshing the key; Vinkius handles secure storage and passing it to the tool.
What happens if I run `get_railcar_details` for a non-existent railcar ID? +
The system returns a specific error message indicating that no record was found. It won't crash your agent; it just tells you the identifier is invalid, allowing your workflow to continue or flag the issue.
How does `arrive_train` handle logging a full train arrival? +
It logs the entire event as a single transaction. You supply the group of cars and the location, and it records the synchronized time stamp for every car in that consist.
What fields must I provide when using `update_work_order`? +
You need the unique work order ID, along with the specific field you want to change (e.g., status or assigned task). You can also include a comment detailing the update reason.
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.
We've already built the connector for Cedar AI. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.