Skip to content

Cursor mcp blockchain_events__blockchain_events_create

How to: Cursor mcp blockchain_events__blockchain_events_create

client:Cursor transport:streamable-http tool:blockchain_events__blockchain_events_create

Add mcp to Cursor

  1. 01

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

{
  "mcpServers": {
    "mcp": {
      "url": "https://ai.cryptoapis.io/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that mcp'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

mcp will not start until these are set, so blockchain_events__blockchain_events_create never becomes available.

  • CRYPTOAPIS_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 21 October 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.