UNICLOUDDB-MCP

What is UNICLOUDDB-MCP?

UNICLOUDDB-MCP is a tool that enables AI assistants to perform CRUD operations on uniCloud databases via the Model Context Protocol (MCP). It runs locally using Node.js (18+) and integrates with cloud functions deployed on uniCloud.

How to use UNICLOUDDB-MCP?

Install the package (npm install uniclouddb-mcp), then configure your MCP client with the command npx -y uniclouddb-mcp and set the DB_SERVICE_URL environment variable to your uniCloud cloud function’s HTTP URL. For local development, copy the mcp_service folder to your uniCloud cloud functions directory, upload the function, and enable URL‑based access. Optionally set REQUEST_TIMEOUT and provide a JSON configuration in your MCP client settings.

Key features of UNICLOUDDB-MCP

• Standardized MCP protocol integration for AI assistants
• Full JQL‑format database operations (query, add, update, remove)
• Simple, easy‑to‑use API
• Compatible with mainstream AI model tool calling
• Supports local execution and source code modification
• Built‑in test tool to verify database connectivity

Use cases of UNICLOUDDB-MCP

• Query documents from a uniCloud collection via natural language requests
• Insert new records or bulk‑add data to a database
• Update existing documents with JQL conditions
• Delete documents based on specified criteria

FAQ from UNICLOUDDB-MCP

What runtime and dependencies are required?

Node.js version 18.0.0 or higher, and a deployed uniCloud cloud function that can process JQL requests.

How do I configure the database connection?

Set the DB_SERVICE_URL environment variable to your uniCloud function’s URL, e.g., https://your‑function‑id.next.bspapp.com/mcp. Optionally adjust REQUEST_TIMEOUT (default 30000 ms).

Which AI models or MCP clients support UNICLOUDDB-MCP?

The package is designed to work with any MCP‑compatible client and adapts to mainstream AI models that support tool calls via the MCP protocol.

Is the tool free and open source?

Yes, it is released under the MIT license. No usage fees are mentioned.

Are there any security considerations?

In production, configure access control and authentication to protect your database endpoint. Avoid exposing the database URL in public environments and keep dependencies updated.