Connect Cursor to Ridekick

A buyer adds Ridekick to Cursor by pasting a block into Cursor's mcp.json. After that, Cursor can look at the buyer's Ridekick requests. Cursor can read. It cannot send a request. The buyer signs in and approves it on a Ridekick screen.

Ridekick in Cursor is available to invited accounts. If sign-in does not work, your account may not be invited yet.

Add Ridekick with an mcp.json block

Open Cursor's mcp.json and add this entry.

{
  "mcpServers": {
    "ridekick": {
      "type": "http",
      "url": "https://www.ridekick.com/api/mcp",
      "auth": {
        "CLIENT_ID": "ridekick-cursor",
        "scopes": [
          "access:read",
          "offers:read"
        ]
      }
    }
  }
}

This block holds no secret. The client is public.

Sign in

When Cursor shows the Ridekick sign-in, the buyer signs in and approves the connection on that Ridekick screen.

What to say first

1. How does Ridekick work? Cursor explains the service.
2. List my Ridekick requests. Cursor reads the buyer's own requests.

If it does not work

If the sign-in is refused, your account may not be invited yet. Do not change the client name in the block: only ridekick-cursor works. Errors from the API are listed in Errors.