Skip to content

Cursor CREW / CrewPay crew_claim_key

How to: Cursor CREW / CrewPay crew_claim_key

client:Cursor transport:streamable-http tool:crew_claim_key

Add CREW / CrewPay to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "crewpay-mcp": {
      "url": "https://mcp.crewpay.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something crew_claim_key does. Cursor lists the server's tools on connect and calls crew_claim_key itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that CREW / CrewPay's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

CREW / CrewPay will not start until these are set, so crew_claim_key never becomes available.

  • CREW_AGENT_API_KEY
  • CREW_LAUNCHER_KEY
  • CREW_API_URL
  • CREWPAY_REFERRAL_CODE
  • X402_EVM_PRIVATE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.