Skip to content
Back to search

cesium-mcp

Protocol-agnostic CesiumJS AI control runtime for MCP, WebMCP, function calling, and browser agents.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/gaopengbin/cesium-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/gaopengbin/cesium-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/gaopengbin--cesium-mcp/badge.svg)](/listings/gaopengbin--cesium-mcp)

HTML

<a href="/listings/gaopengbin--cesium-mcp"><img src="/api/listings/gaopengbin--cesium-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Path 0 — Try in 30 seconds (browser agent, recommended)

Open the [live demo](https://cesium-browser-agent.pages.dev/) and ask—the hosted model is ready without a browser API key: > *"Fly to the Eiffel Tower and drop a red marker"*

Fork the [examples/browser-agent](examples/browser-agent/) folder to deploy your own.

Path 1 — Expose Cesium tools through WebMCP (Chrome 149+ experimental)

The browser-agent example automatically registers all 61 browser-safe page tools plus 3 page-local resource tools when `document.modelContext` is available. Its built-in chat uses automatic toolset routing while keeping resource handles available for large GeoJSON/CZML inputs, and still offers explicit core, single-toolset, and all-tools modes:

npm run build -w packages/cesium-mcp-bridge
npm run build -w packages/cesium-mcp-webmcp
npx serve . -l 4173

Open `http://localhost:4173/examples/browser-agent/`, click **Start**, then inspect or execute the tools in DevTools → Application → WebMCP. Enable `#enable-webmcp-testing` and `#devtools-webmcp-support` in `chrome://flags` for local testing.

Application developers install the adapter separately. End users only open the integrated website; they do not install npm packages or run an MCP server.

npm install cesium-mcp-webmcp
import { registerCesiumViewerWebMcp } from 'cesium-mcp-webmcp/viewer'

const registration = await registerCesiumViewerWebMcp(viewer, {
  toolsets: 'all',
  excludeTools: ['geocode'], // add your own browser geocoder to expose this tool
})

// Later, if the page is unmounted:
registration.unregister()

See the [WebMCP adapter API](packages/cesium-mcp-webmcp/README.md) for custom integrations. For a complete npm + Vite application, start from the [WebMCP integration example](examples/webmcp-integration/).

Path 2 — Embed in your own web app (function calling)

npm install cesium-mcp-bridge
import { CesiumBridge } from 'cesium-mcp-bridge';

const bridge = new CesiumBridge(viewer);
// Then: send the bridge's tool schema to any LLM that supports function/tool calling,
// route the model's tool calls to bridge.execute(name, params).

See [examples/browser-agent/index.html](examples/browser-agent/index.html) for a complete loop with OpenAI-compatible APIs.

Path 3 — Use from Claude Desktop / Cursor / Dify (MCP)

Ordinary MCP users need only the Runtime package. It includes the browser Bridge bundle and a built-in Viewer at `http://localhost:9100/`; install `cesium-mcp-bridge` separately only when integrating a custom page.

# Stable channel — npm latest, MCP SDK v2
npx -y cesium-mcp-runtime

# HTTP mode
npx -y cesium-mcp-runtime --transport http --port 3000

The stable release serves existing MCP `2025-11-25` clients and the new `2026-07-28` protocol from the same stdio/HTTP entry. It uses the stable TypeScript SDK v2 and passes the official `server-stateless` conformance scenario (28/28).

MCP client config:

{
  "mcpServers": {
    "cesium": {
      "command": "npx",
      "args": ["-y", "cesium-mcp-runtime"]
    }
  }
}

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 15 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "cesium-mcp",
  3. "owner": {
  4. "name": "gaopengbin",
  5. "url": "https://github.com/gaopengbin"
  6. },
  7. "plugins": [
  8. {
  9. "name": "cesium-mcp",
  10. "source": "./",
  11. "description": "AI-powered 3D globe control for Claude Code",
  12. "version": "1.2.0"
  13. }
  14. ]
  15. }
README.md · README · 316 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. > **Usage statistics default to on.** Runtime/Dev print a startup notice; browser integrations show a console notice. Set `CESIUM_TELEMETRY_DISABLED=1` (Node), or `globalThis.CESIUM_MCP_TELEMETRY_DISABLED=true` before browser initialization. [Fields, destination and opt-out](https://gaopengbin.github.io/cesium-mcp/guide/telemetry.html).
  2. > [!IMPORTANT]
  3. > ## 📣 作者正在求职 · 北京
  4. >
  5. > **AI 应用开发 · Agent 应用开发 · AI 产品全栈**
  6. >
  7. > 我是高鹏彬,有约 6 年软件开发经验。如果你们团队正在招人,欢迎联系,也感谢帮忙内推或转发!
  8. >
  9. > ### [📄 查看简历 PDF](https://laogao.xyz/platform-api/public/resume/gaopengbin-ai-20260906.pdf) · [✉️ 联系我](mailto:1804287165@qq.com)
  10. >
  11. > [查看我的项目与个人介绍 →](https://github.com/gaopengbin) · 邮箱:**1804287165@qq.com**
  12. > [!TIP]
  13. > **📣 Built with Cesium MCP? / 谁在使用 Cesium MCP?**
  14. >
  15. > Share your project, screenshots, or feedback—work in progress is welcome! / 欢迎分享项目、截图和使用反馈,开发中的作品也欢迎!
  16. >
  17. > **[Share / 分享 → Issue #44](https://github.com/gaopengbin/cesium-mcp/issues/44)** · [Discussion / 讨论区](https://github.com/gaopengbin/cesium-mcp/discussions/43)
  18. <img width="2172" height="724" alt="ChatGPT Image 2026年7月5日 22_13_19" src="https://github.com/user-attachments/assets/098dcbef-e0bc-4214-8adf-b80a29e50e65" />
  19. <div align="center">
  20. <p><strong>A protocol-agnostic Cesium AI control runtime for MCP, WebMCP, function calling, and browser agents</strong></p>
  21. <p><a href="packages/cesium-mcp-bridge/">cesium-mcp-bridge</a> is the protocol-agnostic Cesium command executor. Separate adapters expose it to <strong>browser-only agents</strong>, <strong>WebMCP browser agents</strong>, <strong>function calling</strong>, or <strong>MCP</strong> — your choice.</p>
  22. <p>Four integration paths: <a href="examples/browser-agent/">Browser Agent</a> (simplest, zero backend) · WebMCP (page-local browser tools) · function calling (embed in your web app) · <a href="packages/cesium-mcp-runtime/">MCP runtime</a> (Claude Desktop / Cursor / Dify)</p>
  23. <p>The local Runtime is only required for external MCP hosts. Browser Agent, WebMCP, and function-calling integrations execute the same commands directly in the web application.</p>
  24. <p><a href="https://cesium-browser-agent.pages.dev/"><strong>Try it now</strong></a> — open the live browser demo, no install, no signup.</p>
  25. <p>
  26. <a href="https://gaopengbin.github.io/cesium-mcp/">Website</a> &middot;
  27. <a href="README.zh-CN.md">中文</a> &middot;
  28. <a href="https://gaopengbin.github.io/cesium-mcp/guide/getting-started.html">Getting Started</a> &middot;
  29. <a href="https://gaopengbin.github.io/cesium-mcp/api/bridge.html">API Reference</a>
  30. </p>
  31. <p>
  32. <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-155EEF?style=flat-square" alt="License: MIT"></a>
  33. <a href="https://github.com/gaopengbin/cesium-mcp/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/gaopengbin/cesium-mcp/ci.yml?branch=main&label=CI&style=flat-square" alt="CI"></a>
  34. <a href="https://github.com/gaopengbin/cesium-mcp/stargazers"><img src="https://img.shields.io/github/stars/gaopengbin/cesium-mcp?style=flat-square" alt="GitHub stars"></a>
  35. <a href="https://www.npmjs.com/package/cesium-mcp-runtime"><img src="https://img.shields.io/npm/dm/cesium-mcp-runtime?label=runtime%20downloads&style=flat-square" alt="Runtime downloads"></a>
  36. </p>
  37. <p>
  38. <a href="https://www.npmjs.com/package/cesium-mcp-bridge"><img src="https://img.shields.io/badge/bridge-npm-528bff?style=for-the-badge&logo=npm&logoColor=white" alt="bridge npm"></a>
  39. <a href="https://www.npmjs.com/package/cesium-mcp-runtime"><img src="https://img.shields.io/badge/runtime-npm-155EEF?style=for-the-badge&logo=npm&logoColor=white" alt="runtime npm"></a>
  40. <a href="https://www.npmjs.com/package/cesium-mcp-dev"><img src="https://img.shields.io/badge/dev-npm-364fc7?style=for-the-badge&logo=npm&logoColor=white" alt="dev npm"></a>
  41. </p>
  42. </div>
  43. ---
  44. ## Cesium Map in Codex
  45. Install the hosted map plugin from this repository's **Cesium Map Community** source:
  46. ```text
  47. codex plugin marketplace add gaopengbin/cesium-mcp --ref main
  48. codex plugin add cesium-map@cesium-community
  49. ```
  50. Restart Codex and ask “Open a map of Manhattan.” Uses native host chat, with no local map server or separate model API key. Requires a compatible MCP Apps host. This is a community beta, separate from the OpenAI public directory.
  51. [Installation and compatibility](plugins/cesium-map/README.md) · [ZIP download](https://github.com/gaopengbin/cesium-mcp/releases/tag/cesium-map-plugin-v0.1.0) · [Product website](https://laogao.xyz/cesium-map/)
  52. ### Continue in native Codex chat
  53. - “Open the New York 3D city blocks scene, change the selected building height to 180 metres, then read it back.”
  54. - “Explain the selected hexagon in the San Francisco city activity scene.”
  55. - “Show the Los Angeles hotspots scene, then zoom in on the route.”
  56. Select a scene in the map, click an object and choose **Ask in Codex** to continue with its map context. The host controls chat placement and map expansion.
  57. ### Map previews
  58. ![Cesium Map development preview showing Manhattan's 3D city blocks](docs/public/screenshots/cesium-map/new-york-workspace.jpg)
  59. Actual running screenshot: the development preview is connected to the hosted HTTPS MCP service. The native conversation UI is provided by Codex; it is not pictured here.
  60. | San Francisco · City activity | New York · 3D city blocks | Los Angeles · Hotspots |
  61. | --- | --- | --- |
  62. | ![San Francisco activity hexagons](docs/public/screenshots/cesium-map/san-francisco.jpg) | ![Manhattan illustrative buildings](docs/public/screenshots/cesium-map/new-york.jpg) | ![Los Angeles heatmap and route](docs/public/screenshots/cesium-map/los-angeles.jpg) |
  63. | Inspect feature values and change classification colors | Select buildings, edit extrusion heights and read back properties | Combine a heatmap, markers and connecting routes |
  64. These covers come from rendered map scenes. Buildings, activity values and heatmap points are demonstration data, not surveyed heights or official statistics. Basemap imagery: Esri and its imagery contributors.
  65. ## Demo
  66. https://github.com/user-attachments/assets/8a40565a-fcdd-47bf-ae67-bc870611c908
  67. ## Packages & Entry Points
  68. | Module | Role | Status | Links |
  69. |--------|------|--------|-------|
  70. | **cesium-mcp-contracts** | Transport-neutral names, descriptions, and JSON Schemas for browser tools | New shared layer | [source](packages/cesium-mcp-contracts/) |
  71. | **cesium-mcp-bridge** | Protocol- and transport-free Cesium command executor (60+ commands) | Mainline, actively iterated | [![npm](https://img.shields.io/npm/v/cesium-mcp-bridge)](https://www.npmjs.com/package/cesium-mcp-bridge) · [source](packages/cesium-mcp-bridge/) |
  72. | **cesium-mcp-webmcp** | One-package Viewer integration plus the native `document.modelContext` adapter | Browser integration | [source](packages/cesium-mcp-webmcp/) |
  73. | **examples/webmcp-integration** | Focused npm + Vite integration without a chat UI or MCP server | Developer example | [example](examples/webmcp-integration/) |
  74. | **examples/browser-agent** | Browser-only AI agent with automatic WebMCP exposure | Recommended | [example](examples/browser-agent/) · [live demo](https://cesium-browser-agent.pages.dev/) |
  75. | **cesium-mcp-runtime** | MCP server (stdio + HTTP) | Stable MCP SDK v2 | [![npm](https://img.shields.io/npm/v/cesium-mcp-runtime)](https://www.npmjs.com/package/cesium-mcp-runtime) · [source](packages/cesium-mcp-runtime/) |
  76. | **cesium-mcp-dev** | CesiumJS API knowledge base for coding assistants | Maintained | [![npm](https://img.shields.io/npm/v/cesium-mcp-dev)](https://www.npmjs.com/package/cesium-mcp-dev) · [source](packages/cesium-mcp-dev/) |
  77. > **Which one?** Personal project or quick try → browser-agent. Let a compatible browser agent discover page-local Cesium tools → WebMCP. Existing web app embedding an AI assistant → bridge + your own function calling. Calling from Claude Desktop / Cursor / Dify → MCP runtime.
  78. ## Architecture
  79. ```mermaid
  80. flowchart LR
  81. subgraph clients ["AI Drivers (pick one)"]
  82. BA["Browser Agent\n(in the same page)"]
  83. WM["WebMCP Agent\n(browser-provided)"]
  84. FC["Your web app\nfunction calling"]
  85. MCP["Claude / Cursor / Dify\nvia MCP runtime"]
  86. end
  87. CONTRACTS["cesium-mcp-contracts\ntool definitions"]
  88. WEBMCP["cesium-mcp-webmcp\nnative adapter"]
  89. subgraph core ["cesium-mcp-bridge (browser)"]
  90. B["60+ tools\nprotocol-agnostic dispatcher"]
  91. C["CesiumJS Viewer"]
  92. end
  93. CONTRACTS -.-> BA
  94. CONTRACTS -.-> WEBMCP
  95. BA -- "in-page call" --> B
  96. WM -- "document.modelContext" --> WEBMCP
  97. WEBMCP --> B
  98. FC -- "in-page call" --> B
  99. MCP -- "WebSocket / JSON-RPC" --> B
  100. B --> C
  101. style clients fill:#1e293b,stroke:#528bff,color:#e2e8f0
  102. style core fill:#1e293b,stroke:#12B76A,color:#e2e8f0
  103. ```
  104. The bridge remains the execution core, while contracts and protocol adapters stay separate. Pick whichever driver matches your scenario — they all reach the same Cesium command layer. On WebMCP-capable browsers, `cesium-mcp-webmcp` can expose 61 browser-safe commands in 12 selectable toolsets through `document.modelContext` without adding an MCP transport or backend server.
  105. ### Relationship to the CesiumGS AI ecosystem
  106. CesiumGS's newer AI work is split between [`cesiumjs-ai-starter-app`](https://github.com/CesiumGS/cesiumjs-ai-starter-app), a deployable application template, and [`cesiumjs-skills`](https://github.com/CesiumGS/cesiumjs-skills), development-time guidance for coding agents. The earlier [`cesium-ai-integrations`](https://github.com/CesiumGS/cesium-ai-integrations) repository contains the first-generation experiments and community contributions that helped explore this space.
  107. `cesium-mcp` is an independent runtime and integration toolkit, not a continuation of the earlier WebSocket-only reference architecture. Its reusable Bridge and shared contracts work unchanged across browser-only function calling, native WebMCP, standard MCP over stdio/HTTP, and embedded desktop shells. A local WebSocket bridge is used only when an external MCP host needs to reach a live browser Viewer; it is not required for the hosted demo or page-local integrations.
  108. The project author was an early contributor to `CesiumGS/cesium-ai-integrations`, contributing the Imagery server, Terrain server, and unified MCP Gateway. Those experiments informed this project's multi-protocol architecture, while the implementation, release lifecycle, and roadmap remain independent.
  109. ## Quick Start
  110. ### MCP Apps map panel
  111. Open an interactive Cesium map inside a compatible MCP Apps host with `openCesiumMap`. The panel uses existing MCP tools, publishes camera/layer/selection context, and can send a selected object to the conversation. OpenAI global/thread entrypoint metadata is included; availability depends on the host.
  112. Try the local preview with `npm run app:preview -w packages/cesium-mcp-runtime` after `npm ci` and `npm run build`, then open http://127.0.0.1:19311/. See the [MCP Apps guide](docs/guide/mcp-apps.md) for host configuration and verification boundaries.
  113. ### Path 0 — Try in 30 seconds (browser agent, recommended)
  114. Open the [live demo](https://cesium-browser-agent.pages.dev/) and ask—the hosted model is ready without a browser API key:
  115. > *"Fly to the Eiffel Tower and drop a red marker"*
  116. Fork the [examples/browser-agent](examples/browser-agent/) folder to deploy your own.
  117. ### Path 1 — Expose Cesium tools through WebMCP (Chrome 149+ experimental)
  118. The browser-agent example automatically registers all 61 browser-safe page tools plus 3 page-local resource tools when `document.modelContext` is available. Its built-in chat uses automatic toolset routing while keeping resource handles available for large GeoJSON/CZML inputs, and still offers explicit core, single-toolset, and all-tools modes:
  119. ```bash
  120. npm run build -w packages/cesium-mcp-bridge
  121. npm run build -w packages/cesium-mcp-webmcp
  122. npx serve . -l 4173
  123. ```
  124. Open `http://localhost:4173/examples/browser-agent/`, click **Start**, then inspect or execute the tools in DevTools → Application → WebMCP. Enable `#enable-webmcp-testing` and `#devtools-webmcp-support` in `chrome://flags` for local testing.
  125. Application developers install the adapter separately. End users only open the integrated website; they do not install npm packages or run an MCP server.
  126. ```bash
  127. npm install cesium-mcp-webmcp
  128. ```
  129. ```js
  130. import { registerCesiumViewerWebMcp } from 'cesium-mcp-webmcp/viewer'
  131. const registration = await registerCesiumViewerWebMcp(viewer, {
  132. toolsets: 'all',
  133. excludeTools: ['geocode'], // add your own browser geocoder to expose this tool
  134. })
  135. // Later, if the page is unmounted:
  136. registration.unregister()
  137. ```
  138. See the [WebMCP adapter API](packages/cesium-mcp-webmcp/README.md) for custom integrations.
  139. For a complete npm + Vite application, start from the [WebMCP integration example](examples/webmcp-integration/).
  140. ### Path 2 — Embed in your own web app (function calling)
  141. ```bash
  142. npm install cesium-mcp-bridge
  143. ```
  144. ```js
  145. import { CesiumBridge } from 'cesium-mcp-bridge';
  146. const bridge = new CesiumBridge(viewer);
  147. // Then: send the bridge's tool schema to any LLM that supports function/tool calling,
  148. // route the model's tool calls to bridge.execute(name, params).
  149. ```
  150. See [examples/browser-agent/index.html](examples/browser-agent/index.html) for a complete loop with OpenAI-compatible APIs.
  151. ### Path 3 — Use from Claude Desktop / Cursor / Dify (MCP)
  152. Ordinary MCP users need only the Runtime package. It includes the browser Bridge bundle and a built-in Viewer at `http://localhost:9100/`; install `cesium-mcp-bridge` separately only when integrating a custom page.
  153. ```bash
  154. # Stable channel — npm latest, MCP SDK v2
  155. npx -y cesium-mcp-runtime
  156. # HTTP mode
  157. npx -y cesium-mcp-runtime --transport http --port 3000
  158. ```
  159. The stable release serves existing MCP `2025-11-25` clients and the new
  160. `2026-07-28` protocol from the same stdio/HTTP entry. It uses the stable
  161. TypeScript SDK v2 and passes the official `server-stateless` conformance
  162. scenario (28/28).
  163. MCP client config:
  164. ```json
  165. {
  166. "mcpServers": {
  167. "cesium": {
  168. "command": "npx",
  169. "args": ["-y", "cesium-mcp-runtime"]
  170. }
  171. }
  172. }
  173. ```
  174. ## 62 Available Command Tools
  175. Tools are organized into **12 toolsets**. Default mode enables 4 core toolsets (30 tools). Set `CESIUM_TOOLSETS=all` for everything, or let the AI discover and activate toolsets dynamically at runtime.
  176. > **Canonical contracts**: Tool descriptions default to English; set `CESIUM_LOCALE=zh-CN` for Chinese. Titles, behavior annotations, localized descriptions, defaults, input validation, MCP output schemas, and structured results all come from the shared JSON Schemas in `cesium-mcp-contracts`. Text `content` remains available for older clients.
  177. | Toolset | Tools |
  178. |---------|-------|
  179. | **view** (default) | `flyTo`, `setView`, `getView`, `zoomToExtent`, `saveViewpoint`, `loadViewpoint`, `listViewpoints`, `exportScene` |
  180. | **entity** (default) | `addMarker`, `addLabel`, `addModel`, `addPolygon`, `addPolyline`, `updateEntity`, `removeEntity`, `batchAddEntities`, `queryEntities`, `getEntityProperties` |
  181. | **layer** (default) | `addGeoJsonLayer`, `addGeoJsonPrimitive`, `listLayers`, `removeLayer`, `clearAll`, `setLayerVisibility`, `updateLayerStyle`, `getLayerSchema`, `setBasemap` |
  182. | **interaction** (default) | `screenshot`, `highlight`, `measure` |
  183. | camera | `lookAtTransform`, `startOrbit`, `stopOrbit`, `setCameraOptions` |
  184. | entity-ext | `addBillboard`, `addBox`, `addCorridor`, `addCylinder`, `addEllipse`, `addRectangle`, `addWall` |
  185. | animation | `createAnimation`, `controlAnimation`, `removeAnimation`, `listAnimations`, `updateAnimationPath`, `trackEntity`, `controlClock`, `setGlobeLighting` |
  186. | tiles | `load3dTiles`, `load3dGaussianSplat`, `loadTerrain`, `loadImageryService`, `loadCzml`, `loadKml`, `setEdgeDisplayMode` |
  187. | trajectory | `playTrajectory` |
  188. | heatmap | `addHeatmap` |
  189. | scene | `setSceneOptions`, `setPostProcess`, `setIonToken` (Runtime only) |
  190. | geolocation | `geocode` |
  191. ## Examples
  192. See [examples/minimal/](examples/minimal/) for a complete working demo.
  193. ## Development
  194. ```bash
  195. git clone https://github.com/gaopengbin/cesium-mcp.git
  196. cd cesium-mcp
  197. npm install
  198. npm run build
  199. npm test
  200. npm run test:contracts
  201. npm run test:schema-compat
  202. npm run test:routing
  203. npm run test:model-tools
  204. npm run eval:model-tools
  205. npm run test:e2e:packed
  206. ```
  207. `test:contracts` is the focused parity gate for MCP Runtime metadata, WebMCP registration, Function Calling definitions, provider Schema portability, and the 60-tool Bridge Executor Registry. Run `test:schema-compat` directly for actionable OpenAI, Azure, VS Code MCP, and WebMCP Schema diagnostics.
  208. `test:routing` evaluates bilingual and multi-intent Browser Agent requests across all 12 toolsets, checking required-tool recall and the 20-tool automatic-routing budget.
  209. `test:model-tools` verifies the provider-neutral multi-turn scoring harness. `eval:model-tools` performs a no-network routing preflight by default; add an explicit provider and `--live` to measure real tool choice, argument validity, and required-tool completion. See [Model Tool Evaluation](docs/guide/model-tool-evaluation.md).
  210. `test:e2e:packed` builds npm tarballs, installs them in a clean temporary project, opens the real Cesium Viewer, and verifies a Runtime-WebSocket-Bridge command round trip.
  211. ## Version Policy
  212. Version format: `{CesiumMajor}.{CesiumMinor}.{MCPPatch}`
  213. | Segment | Meaning | Example |
  214. |---------|---------|--------|
  215. | `1.147` | Runtime/Bridge/Dev major.minor follows the verified CesiumJS `~1.147.0` baseline | `1.147.1` targets CesiumJS 1.147 |
  216. | `.x` | MCP patch — independent iterations for new tools, bug fixes, docs | `1.147.1` → `1.147.2` |
  217. Official CesiumJS releases are reviewed before the compatibility baseline is bumped; the project does not automatically claim support for a newer release without Bridge verification.
  218. ## Related Projects
  219. - [mapbox-mcp](https://github.com/gaopengbin/mapbox-mcp) — AI control for Mapbox GL JS
  220. - [openlayers-mcp](https://github.com/gaopengbin/openlayers-mcp) — AI control for OpenLayers
  221. ## Community
  222. This project recognizes [LINUX DO](https://linux.do/) as a community for open-source exchange, technical discussion, and developer feedback.
  223. ## Star History
  224. [![Star History Chart](https://raw.githubusercontent.com/gaopengbin/cesium-mcp/star-history-data/.github/star-history/chart.svg)](https://github.com/gaopengbin/cesium-mcp)
  225. ## License
  226. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.