Skip to content

Cursor nist nvd mcp server nvd_get_cve

How to: Cursor nist nvd mcp server nvd_get_cve

client:Cursor transport:streamable-http tool:nvd_get_cve

Add nist nvd mcp server to Cursor

  1. 01

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

{
  "mcpServers": {
    "nist-nvd-mcp-server": {
      "url": "https://nist-nvd.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

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

  3. 04

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

nist nvd mcp server will not start until these are set, so nvd_get_cve never becomes available.

  • NVD_API_KEY
  • NVD_REQUEST_TIMEOUT_MS
  • MCP_LOG_LEVEL

Same tool, other clients

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