Connect browser agents, embedded AI assistants, and MCP clients to CesiumJS through one shared command layer.
Camera control, GeoJSON layers, 3D Tiles, terrain, imagery, entities, trajectories, heatmaps, geocoding, and more — organized into 12 selectable toolsets.
Expose page-local tools directly to compatible browsers, or connect MCP clients through the runtime. The v2 preview supports both MCP 2025-11-25 and 2026-07-28.
Shared contracts, a pure Cesium executor, separate protocol adapters, and IDE tooling — install only the layers you need.
Sub-second command execution. Tool call flows from AI agent through the runtime to the browser bridge, and results return instantly.
One command to start: `npx cesium-mcp-runtime`. Add the bridge to your CesiumJS app. Connect your AI agent. That is it.
Major.minor tracks the verified CesiumJS baseline (1.143.x targets Cesium ~1.143.0). Patch versions iterate independently for MCP features.
The diagram below shows the MCP runtime path. WebMCP is a separate browser-native adapter that connects a compatible browser agent directly to the same bridge, without the Node.js runtime or WebSocket transport. Compare the integration modes.
1. Your AI agent sends a natural language request, which the MCP client translates into a tool call.
2. cesium-mcp-runtime receives the call via stdio and forwards it as a WebSocket command.
3. cesium-mcp-bridge executes the command on the CesiumJS Viewer in the browser.
4. Results flow back through the same pipeline to the AI agent.
| Package | Description | Version |
|---|---|---|
cesium-mcp-contracts | Transport-neutral tool contracts and JSON Schemas |  |
cesium-mcp-bridge | Browser SDK — embed in your CesiumJS application |  |
cesium-mcp-webmcp | Native browser WebMCP adapter |  |
cesium-mcp-runtime | MCP Server — 62 command tools (12 toolsets) and 2 resources for AI agents |  |
cesium-mcp-dev | IDE MCP Server — Cesium API docs and code generation |  |