4,000+ servers built on vurb.ts
Vinkius

CERN Open Data MCP Server for CursorGive Cursor instant access to 16 tools to Check Cern Opendata Status, Get Glossary, Get Portal Statistics, and more

MCP Inspector GDPR Free for Subscribers

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

The CERN Open Data MCP Server for Cursor is a standout in the The Unthinkable category — giving your AI agent 16 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "cern-open-data": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install CERN Open Data and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
CERN Open Data
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About CERN Open Data MCP Server

Connect to the CERN Open Data Portal and access the world's largest repository of open particle physics data — over 66,000 datasets from the Large Hadron Collider and LEP experiments.

Cursor's Agent mode turns CERN Open Data into an in-editor superpower. Ask Cursor to generate code using live data from CERN Open Data and it fetches, processes, and writes. all in a single agentic loop. 16 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

  • Dataset Discovery — Search across 66,000+ records with powerful filters for experiment (CMS, ATLAS, ALICE, LHCb, DELPHI, OPERA), collision type (pp, e+e−, Pb-Pb), collision energy (7–13.6 TeV), and physics category
  • Physics Categories — Browse datasets by research topic including Higgs boson, Exotica (Dark Matter, Gravitons, Extra Dimensions, Leptoquarks), B physics, heavy-ion collisions, and more
  • Record Intelligence — Retrieve complete metadata for any record: abstracts, authors with ORCID, DOI, event counts, file listings with ROOT/EOS URIs, and processing configurations
  • Portal Analytics — Get comprehensive statistics across all facets: experiments, collision types, energies, file formats, years, and event count distributions
  • Physics Glossary — Search 1,000+ glossary entries for definitions of particle physics terms, detector components, and analysis techniques
  • Software & Documentation — Find analysis frameworks, reconstruction software, guides, and supplementary materials needed to reproduce published results

The CERN Open Data MCP Server exposes 16 tools through the Vinkius. Connect it to Cursor in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 16 CERN Open Data tools available for Cursor

When Cursor connects to CERN Open Data through Vinkius, your AI agent gets direct access to every tool listed below — spanning particle-physics, open-data, research-datasets, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

check

Check cern opendata status on CERN Open Data

Use this to verify the integration is working correctly before performing data queries. The API uses the InvenioRDM REST framework. Verify CERN Open Data API connectivity and portal status

get

Get glossary on CERN Open Data

Returns term names, definitions, and associated experiments. Covers fundamental particles, detector components, analysis techniques, and physics phenomena. Use this to explain technical physics terms like "luminosity", "transverse momentum", "pseudorapidity", "b-tagging", or "muon spectrometer". Invaluable for science communication and educational contexts. Search the CERN particle physics glossary for term definitions

get

Get portal statistics on CERN Open Data

), record types (Dataset, Documentation, Software, Glossary, Supplementaries), data-taking years, keywords, availability status, and event count distributions. This is the single most informative endpoint for understanding the scope and composition of available CERN data. Get comprehensive CERN Open Data portal statistics and facets

get

Get record on CERN Open Data

Returns the full title, abstract, experiment, authors with ORCID identifiers, collision parameters, publication dates, DOI, file distribution summary (number of files, events, size), usage instructions, and a direct link. Use this after finding a record via search to obtain complete details. Example: recid "1" returns the CMS BTau primary dataset. Get detailed metadata for a specific CERN Open Data record

get

Get record by doi on CERN Open Data

Returns the resolved record ID, title, experiment, type, and direct link if found. Useful when you have a DOI from a publication or reference and need to find the corresponding open dataset. DOIs follow the format "10.7483/OPENDATA.CMS.XXX". Returns a "not found" result if the DOI does not match any record. Resolve a DOI to a CERN Open Data record

list

List categories on CERN Open Data

Returns category names and dataset counts. Categories span the full range of particle physics research: Higgs boson searches, exotic particles (Dark Matter, Extra Dimensions, Gravitons), B physics, heavy-ion collisions, and more. Subcategories within Exotica and Higgs Physics provide finer granularity. List all physics categories and subcategories with dataset counts

list

List experiments on CERN Open Data

Currently includes CMS (the largest contributor with ~52,000 datasets), DELPHI (LEP era), ATLAS, ALICE, LHCb, OPERA (neutrino physics), TOTEM, JADE, and PHENIX. Use this as a starting point to understand what data is available before drilling into specific experiments. List all available CERN experiments and their dataset counts

list

List record files on CERN Open Data

Returns filename, size in bytes, checksum, ROOT/EOS URI for direct data access, and file format. Useful for understanding what data is available in a dataset before downloading. Large datasets may contain hundreds of ROOT files. Example: record 1 contains AOD format files from CMS BTau data. List all data files in a CERN Open Data record

search

Search by category on CERN Open Data

Major categories include: Exotica (~13,000 datasets, including Dark Matter, Extra Dimensions, Gravitons, Heavy Fermions, Leptoquarks), Higgs Physics (~10,400, Standard Model and Beyond Standard Model), Higgs (~10,700), Beyond 2 Generations (~1,600), 2 Fermion (~1,200), B physics and Quarkonia (~500), 4 Fermion (~380), Heavy-Ion Physics (~220). Some categories have subcategories — use the subcategory parameter for more precise filtering. Search datasets filtered by physics category

search

Search by collision energy on CERN Open Data

Available energies include: 13TeV (~50,500 datasets, LHC Run 2), 181-210 GeV (~11,700, LEP2), 7TeV (~1,100, LHC Run 1), 8TeV (~900, LHC Run 1), 5.02TeV (~310, heavy-ion), 2.76TeV (~120, heavy-ion), 130-140 GeV (~120, LEP), 13.6TeV (LHC Run 3). The vast majority of data comes from 13 TeV proton-proton collisions at the LHC. Search datasets filtered by collision energy

search

Search by collision type on CERN Open Data

Available collision types: pp (proton-proton, ~52,000 datasets), e+e- (electron-positron, ~12,700), Pb-Pb (lead-lead, ~140), pPb (proton-lead, ~140). Proton-proton collisions from the LHC dominate the dataset. Electron-positron data comes primarily from the LEP era (DELPHI). Use this to focus on a specific collision topology. Search datasets filtered by particle collision type

search

Search by experiment on CERN Open Data

Available experiments include CMS (~52,000 datasets), DELPHI (~12,700), ATLAS (~160), ALICE (~150), LHCb (~108), OPERA (~900), and TOTEM. Combine with a text query for targeted searches within an experiment. This is the fastest way to scope results to a single collaboration. Search datasets filtered by a specific LHC experiment

search

Search datasets on CERN Open Data

Supports full-text queries combined with filters for experiment, collision type, collision energy, physics category, file type, and year. Returns paginated results with metadata including record ID, title, abstract, event counts, file sizes, and direct links. Use this as the primary discovery tool for finding specific physics data. Example queries: "Higgs boson", "dark matter", "top quark pair production". Search CERN Open Data datasets with full-text query and filters

search

Search documentation on CERN Open Data

Returns document titles, abstracts, subtypes (Guide, Policy, About, Activities, Authors, Report, Help, Stripping), and direct links. Use this to find instructions on how to use specific datasets, understand detector configurations, or learn about data processing workflows. Search CERN guides, policies, and documentation

search

Search software on CERN Open Data

Returns software title, description, associated experiment, and subtypes (Analysis, Framework, Tool, Validation, Workflow). Use this to find reconstruction software, analysis frameworks like CMSSW, or specific analysis code associated with published physics results. Search CERN analysis software, frameworks, and tools

search

Search supplementaries on CERN Open Data

These ~5,900 records provide the technical context needed to reproduce physics analyses. Filter by subtype to find specific configuration types. Essential for researchers reproducing or extending published analyses. Search CERN supplementary materials and configurations

Connect CERN Open Data to Cursor via MCP

Follow these steps to wire CERN Open Data into Cursor. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
03

Save the file

Cursor will automatically detect the new MCP server
04

Start using CERN Open Data

Open Agent mode in chat and ask: "Using CERN Open Data, help me...". 16 tools available

Why Use Cursor with the CERN Open Data MCP Server

Cursor AI Code Editor provides unique advantages when paired with CERN Open Data through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

CERN Open Data + Cursor Use Cases

Practical scenarios where Cursor combined with the CERN Open Data MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for CERN Open Data in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with CERN Open Data immediately.

01

"Show me the available experiments and how many datasets each one has on CERN Open Data."

02

"Search for Dark Matter datasets from the CMS experiment at 13 TeV."

03

"What does 'luminosity' mean in particle physics? Check the CERN glossary."

Troubleshooting CERN Open Data MCP Server with Cursor

Common issues when connecting CERN Open Data to Cursor through Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

CERN Open Data + Cursor FAQ

Common questions about integrating CERN Open Data MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Explore More MCP Servers

View all →