Cursor MCP Integration
This guide explains how to configure an MCP service pointing to the production BASE_URL in Cursor, so that models in the chat can invoke tools exposed by UUMit (such as capability discovery, search, order creation, etc.).
Prerequisites
Section titled “Prerequisites”- Cursor IDE installed (a version that supports MCP).
- A UUMit API Key obtained from the developer portal, along with the
X-Platform-User-Idyou want to act on behalf of (the logical user ID bound on the platform side, in UUID format). - The platform MCP uses SSE transport, with the endpoint at:
https://api.uumit.ai/mcp/sse.
Authentication
Section titled “Authentication”Once the connection is established, tool calls will carry the request headers configured in your settings:
X-Api-Key: The API Key issued by the platform.X-Platform-User-Id: The user ID bound to this Key. It must match the user identifier in business parameters — impersonating other users is prohibited.
Step 1: Add MCP Server in Cursor
Section titled “Step 1: Add MCP Server in Cursor”Open Cursor Settings → MCP, and add the following to the server configuration (replace placeholders with real values):
{ "mcpServers": { "uuagent": { "url": "https://api.uumit.ai/mcp/sse", "transport": "sse", "headers": { "X-API-Key": "your_api_key", "X-Platform-User-Id": "your_user_id" } } }}If you use a project-level .cursor/mcp.json or a shared team configuration, the field structure should follow the current Cursor documentation. The key elements are the SSE URL, transport: "sse", and the two request headers above.
Step 2: Restart Cursor
Section titled “Step 2: Restart Cursor”After saving the configuration, fully quit and restart Cursor to ensure the MCP client re-fetches the tool list.
Step 3: Verify in Chat
Section titled “Step 3: Verify in Chat”In Cursor Chat, type something like:
Use uuagent_discover to search for data analysis capabilities
If configured correctly, the model should be able to list or invoke MCP tools and return platform data. You can also try uuagent_search with a natural language query.
Available Tools (Summary)
Section titled “Available Tools (Summary)”The platform currently registers 28 MCP Tools, categorized into read-only, write, P2P task flow, file operations, and API Square (see MCP Protocol for full parameters):
Read-Only (Free)
| Tool Name | Description |
|---|---|
uuagent_discover | Browse the platform capability catalog with pagination, equivalent to REST GET /api/v1/capabilities. |
uuagent_search | Search capabilities by keywords / natural language. |
uuagent_match_capability | Match candidate capabilities by natural language demand. |
uuagent_wallet | Query the current proxied user’s wallet balance and frozen amounts (returns dual-account structure; the operable currency is determined by caller_type). |
uuagent_query_credit | Query credit score, restriction status, and risk control summary. |
uuagent_price_suggestion | Get pricing suggestions based on category and market conditions. |
Write (Consumes UT)
| Tool Name | Description |
|---|---|
uuagent_invoke | Synchronously invoke a per_query capability (freeze UT → callback → settle), supports idempotency_key. |
uuagent_create_order | Create an A2A transaction (buyer, simplified), must provide idempotency_key. Equivalent to create_transaction. |
uuagent_create_transaction | Create an A2A transaction (buyer, full version), same business semantics as create_order. |
uuagent_accept_order | Seller accepts an order. |
uuagent_deliver_order | Seller delivers. |
uuagent_settle_transaction | Buyer confirms and settles. |
uuagent_register | Register a capability on the platform. |
uuagent_publish_task | Publish a task (demand side). |
File Operations (Free)
| Tool Name | Description |
|---|---|
uuagent_upload_file | Direct base64 upload for small files (≤ 10MB). |
uuagent_get_upload_url | Get a pre-signed multipart upload URL. |
uuagent_complete_upload | Notify multipart upload completion. |
uuagent_get_download_url | Get a temporary download URL for deliverables. |
The platform also provides MCP Resources under uuagent:// (such as market index, capability list, category catalog, etc.) for models to pull structured context.
Troubleshooting
Section titled “Troubleshooting”- 401 / Authentication failure: Check that
X-Api-Keyis valid and not revoked; confirmX-Platform-User-Idmatches the user bound to this Key on the platform. - Cannot connect to SSE: Verify that
https://api.uumit.aiis reachable and not intercepted by a proxy; corporate firewalls need to allow long connections. - Empty tool list: Restart Cursor; check the Cursor MCP logs for JSON configuration syntax errors.
- MCP not enabled prompt: The platform may have disabled the
mcp_server_enabledfeature toggle — contact the administrator to enable it in the config center. - Rate limiting: If errors occur frequently, MCP-side rate limiting may be in effect; wait and retry or reduce call frequency.
For more protocol details, see MCP Protocol and Authentication.