How do I find my KDniao EBusinessID and AppKey?

Log in to the [KDniao Portal](https://www.kdniao.com/), go to the 'User Center' or 'API Management' section, and you will find your unique EBusinessID and AppKey for integration.

What is the 'CustomerName' parameter?

For some carriers like Shunfeng (SF) and ZTO, KDniao requires the last 4 digits of the recipient's phone number in the 'CustomerName' field to retrieve tracking data.

Can I query shipping price estimates?

Yes. Use the `query_price` tool with the carrier code, origin city, destination city, and weight to retrieve estimated costs for that specific shipment.

KDniao MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: KDniao
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to KDniao through Vinkius, pass the Edge URL in the `mcps` parameter and every KDniao tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="KDniao Specialist",
    goal="Help users interact with KDniao effectively",
    backstory=(
        "You are an expert at leveraging KDniao tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in KDniao "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About KDniao MCP Server

Empower your AI agent to orchestrate your logistics and e-commerce operations with KDniao (快递鸟), one of the most reliable logistics tracking APIs in China. By connecting KDniao to your agent, you transform complex shipment monitoring, digital waybill management, and delivery forecasting into a natural conversation. Your agent can instantly track packages across hundreds of carriers, identify shippers from tracking numbers, subscribe to status updates, and even estimate arrival times without you ever needing to navigate the comprehensive KDniao portal. Whether you are conducting a supply chain audit or providing real-time customer support for order deliveries, your agent acts as a professional logistics assistant, keeping your data accurate and your operations efficient.

When paired with CrewAI, KDniao becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call KDniao tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Comprehensive Tracking — Retrieve real-time status and historical traces for any supported domestic or international package.
Shipper Identification — Automatically identify the most likely shipper company for a given tracking number.
Update Subscriptions — Set up automated push notifications to receive real-time alerts when a package status changes.
Logistic Estimations — Retrieve shipping price estimates and predicted arrival times for specific routes.
Verification Support — Identify carriers that require additional recipient verification (like phone number digits).

The KDniao MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect KDniao to CrewAI via MCP

Follow these steps to integrate the KDniao MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from KDniao

Why Use CrewAI with the KDniao MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with KDniao through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

KDniao + CrewAI Use Cases

Practical scenarios where CrewAI combined with the KDniao MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries KDniao for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries KDniao, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain KDniao tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries KDniao against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

KDniao MCP Tools for CrewAI (8)

These 8 tools become available when you connect KDniao to CrewAI via MCP:

create_electronic_waybill

Sender/Receiver must be JSON with Name, Mobile, ProvinceName, CityName, ExpAreaName, Address. Uses RequestType 1007. Create an electronic shipping waybill

get_estimated_arrival

Uses RequestType 8001. Get estimated delivery time

identify_carrier

Uses RequestType 2002. Auto-detect carrier from tracking number

onsite_pickup

Uses RequestType 1801. Request on-site courier pickup

preorder_pickup

Uses RequestType 1001. Schedule a courier pickup

query_shipping_price

Uses RequestType 1003. Get shipping price estimate

subscribe_tracking

Uses RequestType 1008. Subscribe to tracking updates via webhook

track_package

Uses RequestType 1002. Track a package in real-time

Example Prompts for KDniao in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with KDniao immediately.

"Track package 'YTO123456789' using carrier code 'YTO'."

"Identify the shipper for tracking number '7890123456'."

"Estimate arrival time for an SF Express package from Shanghai to Hangzhou."

Troubleshooting KDniao MCP Server with CrewAI

Common issues when connecting KDniao to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

KDniao + CrewAI FAQ

Common questions about integrating KDniao MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.