This server (UniCloudDB-MCP) provides standard CRUD operations for uniCloud databases via the MCP protocol, supporting AI assistant integration.
Query data: Retrieve data from a specified collection using JQL format conditions, with options to select fields, limit results, skip records, and sort.
Add data: Insert new data (object or array) into a specified collection.
Update data: Modify existing data in a collection based on JQL conditions.
Remove data: Delete data from a collection based on JQL conditions.
Enables configuration of database service parameters through environment variables, supporting service URL and timeout settings
Required runtime environment for the MCP server with minimum version requirement of 18.0.0
Used for package distribution and installation, with commands for starting the server in standard and development modes
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@UniCloudDB-MCP query users collection where status equals 'active' limit 10"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
基于 MCP 协议的 uniCloud 数据库操作工具，支持通过 AI 助手进行数据库 CRUD 操作。
支持标准化的 MCP 协议工具集成
提供完整的 JQL 格式数据库操作接口
支持查询、添加、更新和删除等常用操作
简单易用的 API 设计
适配主流的 AI 模型工具调用
支持本地运行，修改源码
{
"uniclouddb-mcp": {
"command": "npx",
"args": ["-y", "uniclouddb-mcp"],
"env": {
"DB_SERVICE_URL": "https://你的uniCloud云函数URL.next.bspapp.com/mcp"
}
}
}Related MCP server: Database MCP Server
npm install uniclouddb-mcp你可以通过环境变量配置数据库服务参数：
# config 文件
DB_SERVICE_URL=https://你的uniCloud云函数URL/mcp
REQUEST_TIMEOUT=30000设置通过HTTP或HTTPS访问本云函数的URL。域名在云函数列表界面绑定，此处仅设置path。 参考文档: https://uniapp.dcloud.io/uniCloud/http
{
"uniclouddb": {
"name": "uniclouddb",
"key": "uniclouddb",
"command": "node",
"args":[
"D:\\uniCloudDB-mcp\\index.js"
],
"disabled": false,
"env": {}
}
}本库提供以下 MCP 工具，可供 AI 助手直接调用：
参数：
collection: 集合名称
where: 查询条件（JQL 格式）
field（可选）: 返回字段
limit（可选）: 返回数量限制
skip（可选）: 跳过记录数
orderBy（可选）: 排序条件
参数：
collection: 集合名称
data: 要添加的数据（object/array）
参数：
collection: 集合名称
where: 更新条件（JQL 格式）
data: 要更新的数据（object）
参数：
collection: 集合名称
where: 删除条件（JQL 格式）
使用内置测试工具验证数据库连接和基本功能：
npm testNode.js >= 18.0.0
已部署的 uniCloud 云函数
本工具需要搭配 uniCloud 云函数使用，请确保已部署对应的处理函数。 云函数接收标准 JQL 格式请求，处理数据库操作并返回结果。
生产环境中建议配置访问控制和身份验证
避免在公开环境中暴露数据库 URL
定期更新依赖包以修复潜在安全问题
MIT
| Name | Required | Description | Default |
|---|---|---|---|
| collection | Yes | 集合名称 | |
| data | Yes | 要添加的数据 (object/array) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| collection | Yes | 集合名称 | |
| where | Yes | 查询条件 (JQL格式) | |
| field | No | 返回字段 (可选) | |
| orderBy | No | 排序条件 (可选) | |
| limit | No | 限制返回数量 (可选) | |
| skip | No | 跳过记录数 (可选) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| collection | Yes | 集合名称 | |
| where | Yes | 查询条件 (JQL格式) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| collection | Yes | 集合名称 | |
| where | Yes | 查询条件 (JQL格式) | |
| data | Yes | 要更新的数据 (object) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The four tools have clearly distinct purposes based on their names: add, query, remove, and update correspond to the fundamental CRUD operations. There is no overlap or ambiguity between them, as each targets a specific action in a database context.
All tool names follow a consistent pattern using simple, single-word verbs (add, query, remove, update). There are no deviations in style or convention, making them predictable and easy to understand as a set.
With 4 tools, this server is well-scoped for a database management purpose, covering the essential CRUD operations. Each tool earns its place without being excessive or insufficient for the apparent domain of data handling.
The tool set provides complete CRUD coverage for a database domain: add (create), query (read), update (update), and remove (delete). There are no obvious gaps, as these operations form a full lifecycle for data management without dead ends.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
GibsonAI MCP server: manage your databases with natural language
Hosted MCP server for AI-driven data ops. Create apps, manage schemas, and CRUD structured data.
An agent-native database over MCP: shared, validated, structured records in every AI chat.
Cloud-hosted MCP server for secure AI access to enterprise data sources via CData Connect AI.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/6June6/uniclouddb-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
