Shansong Swift Delivery MCP. Track live GPS, calculate fees, and dispatch orders automatically.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Shansong Swift Delivery MCP Server connects your AI agent directly into Shansong's P2P logistics network. It lets you estimate delivery routes, dispatch riders instantly, and track live GPS locations for any order.
Use it to manage the entire last-mile process without touching a dashboard.
What your AI agents can do
Add tip
Adds a monetary tip to encourage a driver to pick up an order faster.
Calculate fee
Determines the final cost of a delivery route before placing an official order.
Cancel order
Stops a live delivery dispatch that needs to be canceled for any reason.
Gets live GPS coordinates of the Shansong rider assigned to an order.
Calculates the total fee for a delivery route before dispatching an order.
Submits a complete, actionable new Shansong delivery order payload.
Retrieves the live status details for any existing order ID.
Can cancel a dispatch, confirm goods pickup, or add tips to incentivize the rider.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Shansong Swift Delivery: 10 Tools for Logistics
Manage every stage of the delivery lifecycle—from estimating costs to tracking real-time rider movement—using these ten specialized tools.
019d847eadd tip
Adds a monetary tip to encourage a driver to pick up an order faster.
019d847ecalculate fee
Determines the final cost of a delivery route before placing an official order.
019d847ecancel order
Stops a live delivery dispatch that needs to be canceled for any reason.
019d847econfirm goods
Marks the shipment as successfully picked up from the origin location.
019d847ecreate order
Generates and submits a brand new delivery order into the Shansong network.
019d847equery city list
Fetches a list of all active cities where Shansong currently operates services.
019d847equery order info
Retrieves the current, live status and details for an existing order ID.
019d847equery rider position
Gets real-time GPS coordinates of the assigned Shansong rider.
019d847equery store list
Lists all available stores within a specific city for routing purposes.
019d847esubmit complaint
Submits an official complaint against the assigned rider through the system.
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 Shansong Swift Delivery, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
Shansong Swift Delivery MCP Server connects your AI agent straight into Shansong’s Point-to-Point logistics network. It handles the whole last mile—you don't gotta touch any dashboards, you just tell your agent what needs doing. You can manage everything from figuring out costs to tracking where that rider is right now.
To get started, you first need to know where Shansong operates; use query_city_list to pull up every active city they service. When you're planning a route, you gotta check the local stops; running query_store_list lets your agent list all available stores within a specific area for precise routing purposes. Before generating anything, you run calculate_fee to determine the final cost of a delivery route.
This confirms the budget before you commit.
Ready to send it out? You use create_order to generate and submit a brand new delivery order payload into the Shansong network. Once that's done, your agent can mark the goods as officially picked up from the origin point by executing confirm_goods. If things change fast—say, you need to stop the dispatch for some reason—you hit cancel_order to halt a live delivery immediately.
While it's en route, you keep tabs on everything. You can get real-time GPS coordinates of the assigned Shansong rider using query_rider_position. For any existing order ID, running query_order_info gives your agent the current status and all the live details about that package. If the rider needs extra motivation to pick up an order faster, you can add a monetary tip directly with add_tip.
If something goes wrong—maybe the service is bad or the delivery was botched—you submit an official complaint against the assigned rider using submit_complaint.
This setup gives your agent total control over the entire logistics lifecycle. You initiate the process by establishing the order, monitor it minute-by-minute with live tracking and status checks, and you can intervene immediately whether that means canceling a job, confirming pickup, or making sure the driver gets the incentive they need.
How Shansong Swift Delivery MCP Works
- 1 First, sign up on the Shansong Open Platform and register your application. Get your Client ID, App Secret, and Shop ID.
- 2 Push these three variables into Vurb. The node extension generates the required 'Sign' string by converting your JSON payload to an MD5 Hash for their network.
- 3 Your AI agent can now use the tools—like
create_orderorquery_rider_position—to interact with the live delivery system.
The bottom line is, you get a direct API bridge into Shansong's operational systems, letting your AI client handle logistics tasks without needing human intervention on external websites.
Who Is Shansong Swift Delivery MCP For?
This server is for the operations engineer who gets tired of clicking through multiple dashboards just to answer 'Where is my package?' It’s built for teams that need real-time, automated control over physical movement and dispatch logistics.
Uses calculate_fee before sending out new orders and uses create_order to formally initiate the trip.
Runs query_rider_position instantly within a chat context to give customers live GPS updates on their package.
Uses cancel_order or submit_complaint autonomously when a delivery goes wrong, logging the incident immediately.
What Changes When You Connect
- Real-time location updates: Stop asking agents to manually check tracking sites. Using
query_rider_positionlets your agent stream the rider's exact coordinates directly into a chat response. - Automated cost verification: Never guess shipping rates again. Before committing to an order, run
calculate_feeto get the definitive price structure for the route. - Full lifecycle control: Need to stop or change an order? Your agent handles it with
cancel_order, submitting the payload instantly and keeping your workflow clean. - Instant dispatching: From estimating costs to submitting the final request, you can execute a complete logistics flow—
calculate_feefollowed bycreate_order—in one sequence. - Proactive support handling: Instead of waiting for customers to ask 'Where is it?', your agent can proactively call
query_order_infoand report status updates automatically.
Real-World Use Cases
Handling a delayed shipment query
A customer texts, 'What's wrong with order SS991024?' The agent immediately calls query_order_info to confirm the status. Then, it uses query_rider_position to give the customer live GPS data, confirming exactly where the rider is right now.
Setting up a new drop-off point
A coordinator needs to ship documents from Store A to Store B. The agent first calls query_store_list for both locations, then uses calculate_fee with the coordinates to confirm the price before finally calling create_order.
Correcting a misassigned rider
The initial driver is struggling. The agent first calls submit_complaint against the assigned rider for poor performance, then uses cancel_order to pull the job, allowing dispatchers to reassign it immediately.
Completing a tricky pickup
Goods were dropped off but the system hasn't logged them. The agent first calls confirm_goods and then uses add_tip on the successful delivery record to thank the rider for their help.
The Tradeoffs
Trying to manage status updates
Writing a series of steps like: '1. Go to Order Dashboard. 2. Click Status tab. 3. Manually input the new time.' This requires jumping between multiple external web pages and copy-pasting data.
→
Let your agent handle it end-to-end. Just call query_order_info with the ID, and the system returns all the status changes automatically. No dashboards needed.
Forgetting to check pricing first
Calling create_order without verifying the fee structure. You risk dispatching a job at the wrong cost or missing local surcharges.
→
Always call calculate_fee first. Use that result as validation before you submit the final payload via create_order. It's a necessary two-step check.
Using generic location data
Telling customers 'The rider is near downtown.' This vague statement doesn't help solve their problem and sounds unprofessional.
→
Use query_rider_position to get live coordinates. Your agent can then format this precise data (Lat/Long) into a clean, authoritative customer message.
When It Fits, When It Doesn't
Use this MCP Server if your core business process revolves around managing physical movement: dispatching goods, tracking location in real-time, or handling last-mile logistics. It’s essential when you need to execute complex chains of actions—like checking fees, creating the order, and then querying status—all without human clicks.
Don't use this if your problem is purely informational (e.g., 'What are today's weather forecasts?') or requires accessing internal HR databases. For those cases, you need a different data source type. If you only need to read static lists of cities, query_city_list works, but for actual dispatching and tracking, this is your go-to tool.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Shansong. 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 server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Customer support usually means endless clicks and confusing status pages.
Today, answering 'Where is my order?' requires the agent to log into the Order Dashboard, search by ID, wait for the page to load, read out a vague status (e.g., 'In Transit'), and then potentially open a separate map link—all while the customer waits on hold or in chat.
With this MCP server, your AI client handles it instantly. You just pass the order ID to `query_order_info`. The agent pulls the live status, verifies the last known location using `query_rider_position`, and gives a precise, actionable update—no dashboards involved.
The Shansong Swift Delivery MCP Server: Full control over dispatching.
Manual dispatch requires someone to first check the pricing structure, then manually fill out a form with all parameters (items, addresses), and finally hit 'Submit.' Mistakes here mean lost revenue or failed deliveries.
Now, your agent executes this entire process cleanly. It calls `calculate_fee` for validation, submits the payload via `create_order`, and you're done. The system handles the complexity; you just manage the intent.
Common Questions About Shansong Swift Delivery MCP
How do I get live tracking using query_rider_position? +
You pass an order ID to query_rider_position. This tool returns the real-time GPS coordinates (Latitude and Longitude) of the assigned driver, allowing your agent to provide precise updates.
Do I need to calculate fees before creating an order using calculate_fee? +
Yes. Always run calculate_fee first. This confirms the current rates and total cost for the route. It’s best practice to validate pricing before you call create_order.
What if I need to cancel a delivery, what tool do I use? +
Use cancel_order. This tool sends the cancellation payload to Shansong's system. It handles stopping the dispatch and updating the status internally.
How do I submit a complaint against a driver? +
Call the submit_complaint tool directly. You provide necessary details, and the server submits an official record of the issue to Shansong's system for review.
How do I authenticate my agent to use the `create_order` tool? +
You must provide your Client ID, App Secret, and Shop ID. The Node extension handles authentication by generating a required MD5 Hash signature. This ensures that every dispatch request sent through your AI client is properly authenticated with Shansong's network.
Before calling any dispatch tool, how can I check available cities using `query_city_list`? +
The tool returns a list of all active operating cities. Running this first step confirms that your agent targets a valid geographic area. This prevents errors when calculating fees or attempting to create an order in an unsupported region.
If I need a detailed status update on an existing shipment, how does `query_order_info` work? +
This tool provides comprehensive details about the entire order lifecycle. It returns current statuses beyond just location, including key milestones like 'picked up' or 'out for delivery'. You get a full view of where the order stands.
What process does `confirm_goods` handle after a successful pick-up? +
This action formally registers that the goods were successfully picked up at the source location. It completes the first critical leg of the journey, telling Shansong's system to move the order into the official dispatch queue for routing.
How is the Shansong API payload encrypted? +
Instead of demanding complex LLM scripting to assemble clientId, JSON stringification, and MD5 encoding, this plugin seamlessly abstracts the sign variable creation. All HTTP form-data bounds are strictly governed locally on the proxy instance yielding instant results.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Amilia
Recreation and activity management — manage programs, accounts, and registrations via AI.
Typefully
Write, schedule, and grow your audience on Twitter and LinkedIn with an editor that helps you craft threads that go viral.
B5 Arena
Automate Counter-Strike intelligence via B5 Arena — scan matchmaking leaderboards, track player ELO, and fetch competitive match logs natively from any AI agent.
You might also like
RCSB PDB
Explore 220K+ 3D molecular structures — search proteins, DNA, and RNA by name, experimental method, resolution, and bound ligands from the Protein Data Bank.
NHTSA Vehicle Safety
Decode VINs, search recalls and complaints, check safety ratings and find car seat inspection stations.
Gotify
Send and receive push notifications via your own Gotify server — manage messages, applications, and clients directly through AI.