Cesium Mcp Runtime
@gaopengbin
MCP server that enables AI agents to control CesiumJS 3D globe with natural language. Supports camera flight, entity management, imagery layers, terrain, GeoJSON, trajectory playback, and interactive picking. Works with Claude Desktop, VS Code Copilot, Cursor and any MCP-compatib
Overview
What is Cesium Mcp Runtime?
Cesium Mcp Runtime is a Node.js server that bridges AI agents (via the Model Context Protocol) to a CesiumJS 3D globe viewer. It provides 19 MCP tools and 2 resources that let you control camera, entities, layers, terrain, and interactions using natural language. It is designed for developers building AI-powered geospatial applications with CesiumJS.
How to use Cesium Mcp Runtime?
Install cesium-mcp-bridge in your CesiumJS application, register the viewer with CesiumMCPBridge.register(viewer), then configure your MCP client to run npx cesium-mcp-runtime as the server command.
Key features of Cesium Mcp Runtime
- 19 MCP tools for full CesiumJS control via natural language
- Camera: flyTo, setView, getView, zoomToExtent
- Entities: addMarker, addLabel, highlight, removeLayer
- Layers: loadImageryService, load3dTiles, addGeoJsonLayer, addHeatmap
- Terrain: loadTerrain, setBasemap
- Interaction: screenshot, playTrajectory
- 2 resources: scene state and entity list
- Architecturally bridges AI ↔ MCP stdio ↔ Node.js ↔ WebSocket ↔ Browser ↔ CesiumJS Viewer
Use cases of Cesium Mcp Runtime
- AI agent controlling a 3D globe by voice or chat commands
- Automatically adding markers, labels, and GeoJSON layers to a CesiumJS scene
- Flying the camera to specific coordinates or extents on demand
- Taking screenshots or replaying trajectories through AI requests
- Loading 3D Tiles, imagery services, and terrain without manual code
FAQ from Cesium Mcp Runtime
What MCP tools does Cesium Mcp Runtime provide?
It provides 19 tools covering camera control, entity management, layer loading, terrain/basemap switching, and interaction (screenshot, playTrajectory).
How does Cesium Mcp Runtime connect to CesiumJS?
The server communicates via WebSocket to a browser-side bridge (cesium-mcp-bridge) that must be registered with the CesiumJS viewer.
What are the installation steps?
Install cesium-mcp-bridge in your CesiumJS app, call CesiumMCPBridge.register(viewer), then configure your MCP client to run npx cesium-mcp-runtime.
What runtime environment is required?
The server requires Node.js (to run cesium-mcp-runtime) and a browser running a CesiumJS application with the bridge injected.
Does Cesium Mcp Runtime store any data persistently?
No. The README does not mention any persistent storage; data and scene state exist only in the browser’s CesiumJS viewer during the session.
