Skip to content

Cursor cern-inspire-mcp-server cern_inspire_search_hepdata

How to: Cursor cern-inspire-mcp-server cern_inspire_search_hepdata

client:Cursor transport:streamable-http tool:cern_inspire_search_hepdata

Add cern-inspire-mcp-server to Cursor

  1. 01

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

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

    Save the file and restart Cursor.

  2. 03

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

  3. 04

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

cern-inspire-mcp-server will not start until these are set, so cern_inspire_search_hepdata never becomes available.

  • MCP_LOG_LEVEL

Same tool, other clients

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