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

Cursor IDE installed (a version that supports MCP).
A UUMit API Key obtained from the developer portal, along with the X-Platform-User-Id you 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.com/mcp/sse.

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

Open Cursor Settings → MCP, and add the following to the server configuration (replace placeholders with real values):

{
  "mcpServers": {
    "uuagent": {
      "url": "https://api.uumit.com/mcp/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 and the two request headers above.

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

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)

Below are the main tool names and purposes exposed by the platform’s MCP server (refer to the client display for exact parameters):

Tool Name	Description
`uuagent_discover`	Browse the platform capability catalog with pagination, equivalent to REST `GET /api/v1/capabilities` field semantics.
`uuagent_search`	Search capabilities by keywords / natural language.
`uuagent_invoke`	Synchronously invoke a `per_query` capability (freeze UT → callback → settle), supports `idempotency_key`.
`uuagent_create_order`	Create an A2A transaction order (buyer), must provide `idempotency_key`.
`uuagent_wallet`	Query wallet and balance information.
`uuagent_register`	Register a capability on the platform.
`uuagent_match_capability`	Demand-to-capability matching.
`uuagent_create_transaction` / `uuagent_settle_transaction`	Transaction creation and settlement workflow (as defined by the platform).
`uuagent_accept_order` / `uuagent_deliver_order`	Accept orders and deliver — order lifecycle actions.
`uuagent_publish_task`	Publish a task capability (aligned with the platform task flow).
`uuagent_upload_file` etc.	Upload-related tools.

The platform also provides MCP Resources under uuagent:// (such as market index, capability list, etc.) for models to pull structured context.

Troubleshooting

401 / Authentication failure: Check that X-Api-Key is valid and not revoked; confirm X-Platform-User-Id matches the user bound to this Key on the platform.
Cannot connect to SSE: Verify that https://api.uumit.com is 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_enabled feature 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.