How do I find my Xiaomi App Secret?

Log in to the [Xiaomi Open Platform console](https://dev.mi.com/console/), navigate to the 'Push Service' section, select your application, and you will find your unique App Secret in the application details overview.

Which region should I select?

Select the region where your users are primarily located. `CHINA` uses the Mainland gateway, while `GLOBAL` uses the Singapore gateway. Europe, Russia, and India have dedicated local gateways for better delivery performance.

What is the difference between RegID and Alias?

A RegID is a unique identifier generated by the Xiaomi SDK for each device. An Alias is a custom string (like a username) that you associate with one or more RegIDs in your application code to simplify targeting.

Xiaomi Push Service / 小米推送 MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: Xiaomi Push Service / 小米推送
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

Connect your CrewAI agents to Xiaomi Push Service / 小米推送 through the Vinkius — pass the Edge URL in the `mcps` parameter and every Xiaomi Push Service / 小米推送 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="Xiaomi Push Service / 小米推送 Specialist",
    goal="Help users interact with Xiaomi Push Service / 小米推送 effectively",
    backstory=(
        "You are an expert at leveraging Xiaomi Push Service / 小米推送 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 Xiaomi Push Service / 小米推送 "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 6 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 Xiaomi Push Service / 小米推送 MCP Server

Empower your AI agent to orchestrate your device communication and mobile engagement with Xiaomi Push Service (小米推送), the premier notification platform for the Xiaomi ecosystem. By connecting Xiaomi Push to your agent, you transform complex message sending, alias mapping, and regional broadcasting into a natural conversation. Your agent can instantly send notifications to specific Registration IDs, target users by their custom aliases, and broadcast updates to millions of devices across various regional gateways (China, Global, Europe, India, Russia) without you ever needing to navigate the comprehensive MiPush Console. Whether you are automating high-priority alerts or coordinating a system-wide update, your agent acts as a real-time push coordinator, providing accurate and fast results from a single, authorized source.

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

What you can do

Targeted Orchestration — Send notifications directly to unique Registration IDs or user-defined aliases.
Regional Broadcasting — Reach global audiences by utilizing specialized regional gateways for China, Europe, and more.
Topic Management — Broadcast messages to specific device topics for segmented engagement.
Global Communication — Send broadcast messages to all users registered to your application in one go.
Operational Discovery — Verify RegID formats, check topic length limits, and monitor API connectivity.

The Xiaomi Push Service / 小米推送 MCP Server exposes 6 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 Xiaomi Push Service / 小米推送 to CrewAI via MCP

Follow these steps to integrate the Xiaomi Push Service / 小米推送 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 6 tools from Xiaomi Push Service / 小米推送

Why Use CrewAI with the Xiaomi Push Service / 小米推送 MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Xiaomi Push Service / 小米推送 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 the 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

Xiaomi Push Service / 小米推送 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Xiaomi Push Service / 小米推送 MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Xiaomi Push Service / 小米推送 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 Xiaomi Push Service / 小米推送, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Xiaomi Push Service / 小米推送 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 Xiaomi Push Service / 小米推送 against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Xiaomi Push Service / 小米推送 MCP Tools for CrewAI (6)

These 6 tools become available when you connect Xiaomi Push Service / 小米推送 to CrewAI via MCP:

push_to_alias

Send push to a user alias

push_to_all

Broadcast push to all devices

push_to_regid

Send push to a device registration ID

push_to_topic

Send push to a topic

subscribe_to_topic

Subscribe a device to a topic

unsubscribe_from_topic

Unsubscribe a device from a topic

Example Prompts for Xiaomi Push Service / 小米推送 in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Xiaomi Push Service / 小米推送 immediately.

"Send a push notification to Xiaomi RegID 'ABCD...1234' with title 'Welcome' and body 'Glad to have you here!'."

"Push an urgent alert to user alias 'user_8821' saying 'Your account has a new login'."

"Broadcast a global announcement to all users: 'Maintenance starts at 10 PM tonight'."

Troubleshooting Xiaomi Push Service / 小米推送 MCP Server with CrewAI

Common issues when connecting Xiaomi Push Service / 小米推送 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

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

Xiaomi Push Service / 小米推送 + CrewAI FAQ

Common questions about integrating Xiaomi Push Service / 小米推送 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.