Connect Cursor

Cursor connects to remote MCP servers by URL and can send custom headers, so it talks to your site directly. Its mcp.json can read values from environment variables, which keeps the credential out of the file.

First prepare your site: choose WooCommerce MCP or the MCP Adapter, create the credential and the Raqvio Agent Guardrails agent.

Add the server

Edit ~/.cursor/mcp.json (available in every project) or .cursor/mcp.json inside one project.

WooCommerce MCP (API key):

{
  "mcpServers": {
    "my-store": {
      "url": "https://your-store.example/wp-json/woocommerce/mcp",
      "headers": {
        "X-MCP-API-Key": "${env:STORE_MCP_KEY}"
      }
    }
  }
}

Set STORE_MCP_KEY to your ck_…:cs_… key in the environment Cursor starts from.

MCP Adapter (application password):

{
  "mcpServers": {
    "my-site": {
      "url": "https://your-store.example/wp-json/mcp/mcp-adapter-default-server",
      "headers": {
        "Authorization": "Basic ${env:STORE_BASIC_AUTH}"
      }
    }
  }
}

Set STORE_BASIC_AUTH to the Base64 of user-name:application-password (how to compute it).

If you put the server in a project’s .cursor/mcp.json, keep the credential in the environment variable as shown — not in the file — so it isn’t committed with the project.

Check the connection

Open Cursor’s MCP settings: the server should be listed with its tools enabled. Then check that it works in Raqvio Agent Guardrails’s audit log.