# Model Context Protocol (MCP) server

MongoDB has released a federated Copilot connector for MongoDB Atlas, now generally available, letting users ask Microsoft 365 Copilot questions about live Atlas data. Previously such answers lived in operational applications built on Atlas while the questions were asked in everyday productivity tools, or relied on a static copy of the data. The connector queries Atlas on demand through MongoDB's managed remote MCP server, with no migration or indexed copy, and each query runs as the signed-in user under existing Atlas permissions.

MongoDB has released a federated Copilot connector for MongoDB Atlas, now generally available, letting users ask Microsoft 365 Copilot questions about live Atlas data. Previously such answers lived in operational applications built on Atlas while the questions were asked in everyday productivity tools, or relied on a static copy of the data. The connector queries Atlas on demand through MongoDB's managed remote MCP server, with no migration or indexed copy, and each query runs as the signed-in user under existing Atlas permissions.

The work introduces EvoOntology, which encapsulates an ontology as an MCP server with schema, content, and tool layers, builds an initial ontology via a builder agent issuing probe queries, and continuously refines it through attribution-guided typed edits admitted only after backbone-conditional paired evaluation, consistently outperforming ReAct baselines and static semantic-layer baselines on three data-agent benchmarks with six LLM backbones.

The work introduces EvoOntology, which encapsulates an ontology as an MCP server with schema, content, and tool layers, builds an initial ontology via a builder agent issuing probe queries, and continuously refines it through attribution-guided typed edits admitted only after backbone-conditional paired evaluation, consistently outperforming ReAct baselines and static semantic-layer baselines on three data-agent benchmarks with six LLM backbones.