LeanCloud MCP. Control your backend state via chat, not dashboards.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
LeanCloud MCP Server connects your AI client directly to a backend-as-a-service platform. It lets you manage data classes, user records, and application files without touching a console dashboard.
You can list objects, update users, delete stale data, or even trigger push notifications—all through natural conversation with your agent.
This is for developers who need immediate control over application state.
What your AI agents can do
Create object
Creates a brand new record in any of your defined data classes.
Delete object
Removes an existing object from the database.
Get app stats
Retrieves key metrics about your application's overall usage and health.
List all objects within a data class or retrieve detailed metadata for specific records.
Retrieve full user profiles and list the entire application membership base to audit who's logged in.
Create new records, update existing fields, or delete objects entirely through simple commands.
Fetch current application statistics, including API request counts and storage usage metrics.
Initiate push notifications to engage users instantly when a critical event happens in the system.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
LeanCloud MCP Server: 10 Tools for Backend Control
These ten tools give your AI client full control over creating, reading, updating, deleting records, managing users, and sending notifications in LeanCloud.
019d8451create object
Creates a brand new record in any of your defined data classes.
019d8451delete object
Removes an existing object from the database.
019d8451get app stats
Retrieves key metrics about your application's overall usage and health.
019d8451get object
Fetches the full details for a single, specified data object.
019d8451get user
Retrieves all profile information for one specific user account.
019d8451list files
Lists all the files currently uploaded to your application's cloud storage bucket.
019d8451list objects
Shows a list of every object that exists within a particular data class.
019d8451list users
Returns a comprehensive roster of all registered users in the application.
019d8451push notification
Sends an immediate notification to one or more end-users.
019d8451update object
Modifies and saves changes to an existing data object record.
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 LeanCloud, 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
You’ll connect your AI agent straight into the core of your backend infrastructure using LeanCloud. This server gives your client direct, hands-on access to everything: data classes, user records, file storage, and notifications. You bypass complex web consoles; you just talk to your agent.
Your agent handles all the stuff that used to take multiple clicks across a dozen dashboards. Need an audit? Just ask for it. Wanna write a new record or purge stale junk data? Tell the agent what needs doing. It talks straight to the LeanCloud APIs, giving you real-time control over your whole application state.
Auditing and Managing Your Data
To take stock of your app’s data, you can list every single object in a defined data class using list_objects, or pull up the full details for one specific record with get_object. You've got complete control over that data lifecycle: if you need to make changes, use update_object to modify and save fields on an existing object.
If the data’s garbage, delete_object removes it from the database entirely. To kick off a brand new record, you call create_object, which builds out any structure in your defined data classes.
Handling Users and Membership
For membership management, you've got two tools. You can pull up a comprehensive list of every user who signed up using list_users. If you need to check on one specific profile, get_user fetches all the details for that single account. These functions let you audit your entire user base and track who’s logged in.
System Health and Monitoring
To know how healthy the system is running, call get_app_stats. This function pulls key metrics on your app's overall usage and health. If you need to see what files are sitting in your cloud bucket, run list_files to get a list of every file uploaded.
Real-Time Communications
When something critical happens, don’t wait for an email. You can trigger immediate action by sending push notifications using the push_notification tool, hitting one or more end-users right away.
How LeanCloud MCP Works
- 1 Subscribe to the server and enter your specific LeanCloud App ID and App Key credentials.
- 2 Connect this MCP Server to your preferred AI client (Claude, Cursor, etc.).
- 3 Use natural conversation; tell your agent what data you need or what action must happen. It handles the rest.
The bottom line is: your AI agent treats your entire backend like a single chat interface instead of a dozen dashboards.
Who Is LeanCloud MCP For?
This is for developers and operations teams who get bogged down in clicking through separate web consoles just to perform basic data maintenance. It’s for the product manager who needs to know if User X changed their profile, or the backend engineer who wants to write a script to clean up 10,000 stale records without writing boilerplate API calls.
Uses create_object, update_object, and delete_object to programmatically manage data records during deployment or maintenance cycles.
Manages user growth by running list_users for audits, or triggering a marketing alert using push_notification.
Calls get_app_stats and list_objects to pull system metrics and audit data class usage over time.
What Changes When You Connect
- Manage the full user base with
list_usersandget_user. Audit who belongs in the system or check a single profile instantly—no more digging through membership reports. - Maintain data integrity by using
create_object,update_object, anddelete_objectdirectly. You can write cleaning scripts for your agent, keeping records accurate without writing complex code. - Get immediate visibility into application performance with
get_app_stats. Track API call volume or storage usage right away to spot bottlenecks before they crash the service. - Engage users instantly by calling
push_notification. Instead of waiting for an email batch, trigger an alert the moment a user's profile changes or an event occurs. - Audit your assets using
list_filesandlist_objects. Need to see what data classes exist? Or check if critical documents are uploaded? The agent handles it all.
Real-World Use Cases
Data Cleanup After a Feature Launch
A developer needs to remove temporary staging records. Instead of running multiple DELETE statements in the console, they tell their agent: 'Run delete_object on all objects from the 'staging' class created last month.' The agent executes the required tools and confirms the cleanup.
Membership Audit for Compliance
The ops team needs to check which user accounts have been inactive for 90 days. They ask their agent to run list_users and then filter the results, getting a definitive list of accounts needing investigation.
Real-Time User Onboarding
A new feature goes live that requires user acknowledgment. Instead of relying on email, the agent calls push_notification immediately after a user's profile is created (create_object), ensuring they get instant access instructions.
Debugging Data Flow
A bug report says User Z has incorrect billing data. The engineer asks the agent to run get_user for User Z, and then uses get_object on the specific 'billing' record to see exactly which piece of metadata is wrong.
The Tradeoffs
Treating it like a simple form filler
Trying to manually list every single field for an object just by reading the console output, instead of asking the agent to get_object.
→
Always let your AI client call get_object. It retrieves the full record metadata and presents it in a clean format. Don't eyeball the data; ask for the details.
Assuming all tools do the same thing
Confusing 'listing files' (list_files) with listing database records, which requires list_objects. This causes wasted time and wrong data.
→
Remember: list_files is for cloud storage contents. Use list_objects when you need to see the collection of records inside a specific data class.
Ignoring user history
Writing an update command that doesn't verify if the user exists first, leading to failed updates.
→
Before running update_object, always run get_user or check with list_users. Verify the unique ID first. This prevents invalid operations.
When It Fits, When It Doesn't
Use this server if your workflow requires constant interaction with structured, persistent data—think CRMs, internal dashboards, or membership platforms. You need to read it for user records (get_user, list_users) and write it back using the full CRUD cycle (create_object through update_object). It’s essential when your application state is complex.
Don't use this if you just need a simple, one-off calculation or external data feed. If you only need to check system health metrics without touching user records, maybe another specialized monitoring API is better. This server excels at data governance and state changes, not just read-only reporting.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by LeanCloud. 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
Debugging application state shouldn't mean switching between 5 different admin tabs.
Today, if a user reports bad data, you have to open the User Management console, then switch to the Data Audit tab. You pull the user ID, manually navigate to the 'Billing' class, find that ID again, and check the object details. It’s slow, and you risk cross-referencing IDs wrong.
With the LeanCloud MCP Server, your agent handles it all in one chat. You simply ask: 'Show me the billing data for User XYZ.' The agent runs `get_user` first, then executes `get_object`, giving you the full context right away. It’s fast.
The LeanCloud MCP Server lets you control your entire data lifecycle.
Before this, modifying data meant writing complex REST calls and managing authentication headers for every single operation. If you needed to delete a record or update user permissions, it was boilerplate code that took time away from the actual feature work.
Now, your agent handles state changes with simple commands. You can call `create_object`, then trigger an action like sending a notification via `push_notification`. It turns complex backend logic into conversational instructions.
Common Questions About LeanCloud MCP
How do I list all the users in my application using the list_users tool? +
Just ask your agent to 'List all users.' The list_users tool pulls a comprehensive roster of every account registered on the platform. It's the quickest way to audit membership.
Can I update an object without knowing its ID? +
No. You must first use get_object or list_objects to find the specific ID, and then pass that ID when you call update_object. The system requires a unique identifier for modification.
What is the difference between list_objects and get_object? +
It’s about scope. list_objects gives you a summary—a quick view of every object in a class. You use get_object when you need the full, detailed metadata for just one record.
How do I trigger an alert using push_notification? +
You tell your agent to 'Send a notification about [topic] to [user ID].' The push_notification tool handles the delivery mechanism, ensuring users get real-time alerts.
Can I check my API usage with get_app_stats? +
Yes. Calling get_app_stats pulls key metrics like total API requests and current storage usage. It’s your quick dashboard check for overall application health.
How do I use the `list_files` tool to see all stored documents in my application? +
The list_files tool shows a directory of every file uploaded to your cloud storage. It returns metadata for each file, including its unique ID, creation date, and current size. This lets you audit which assets are available without needing access to the actual files.
What are the required parameters when I call the `create_object` tool? +
You must provide a target data class name and at least one key-value pair of data. The system validates this against your schema, ensuring that all mandatory fields for that object type receive values before creation succeeds.
Besides basic contact info, what detailed metadata does the `get_user` tool retrieve about a user profile? +
The get_user tool pulls more than just names and emails. It retrieves attributes like roles, last login timestamps, associated application usage counts, and any custom fields you've defined for that specific user account.
How do I find my LeanCloud App ID and Key? +
Log in to your LeanCloud console, select your application, and go to [Settings] → [App Keys]. You will find your App ID, App Key, and Master Key there.
When do I need to use the Master Key? +
The Master Key is required for administrative operations that bypass ACLs, such as listing all users, sending push notifications, or retrieving sensitive system metrics. It should be kept strictly confidential.
Can I query custom data classes? +
Yes! Use the list_objects tool and provide the exact name of your data class. Your agent will retrieve the records according to your application's permissions.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Railway
Equip your AI with direct access to your Railway infrastructure — manage projects, deployments, services, and environment variables.
IPRoyal (Proxy Services)
Manage proxies via IPRoyal — monitor traffic, rotate credentials, and manage whitelisted IPs.
Yodiz
Manage user stories, sprints, bugs, and epics on Yodiz — the all-in-one agile project management and issue tracking tool.
You might also like
Guestmeter
Automate guest feedback collection and reputation management via Guestmeter directly from any AI agent.
Adzuna Alternative
Search millions of job advertisements and access real-time labor market analytics, salary trends, and regional vacancy data.
ReferralCandy
Connect your AI agents to ReferralCandy to manage referral programs, track advocates, register purchases, and analyze campaign performance.