# gaopengbin/cesium-mcp [Health: Active]

**Category:** 🗺️ Location Services  
**Repository:** https://github.com/gaopengbin/cesium-mcp  
**GitHub Stars:** 136  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/gaopengbin-cesium-mcp

## Description
AI-powered 3D globe control via MCP. Connect any MCP-compatible AI agent to CesiumJS — camera flight, GeoJSON/3D Tiles layers, markers, spatial analysis, heatmaps, and more through 19 natural language tools.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "cesium-mcp": {
    "command": "npx",
    "args": ["-y","serve"]
  }
}
```

## Documentation

## What gaopengbin/cesium-mcp MCP server does

The gaopengbin/cesium-mcp MCP server exposes CesiumJS operations to AI-driven applications. Its command layer can manipulate a Cesium Viewer, including changing the camera, adding or working with GeoJSON and 3D Tiles layers, placing markers, and running spatial or visualization-oriented operations such as heatmaps.

The repository is organized around several packages rather than a single adapter. `cesium-mcp-bridge` contains the protocol-independent command executor, `cesium-mcp-contracts` defines shared tool names and JSON Schemas, and `cesium-mcp-runtime` provides the MCP server for external hosts. Browser integrations are provided through WebMCP and a browser-agent example, while the bridge can also be embedded in an application using function calling.

## How it works

A browser-based Cesium Viewer remains the execution target. The bridge receives structured commands and applies them to that Viewer, while the selected adapter determines how an agent discovers and invokes those commands. The same execution layer can therefore serve page-local browser agents, native WebMCP, application-specific function calling, or a standard MCP client.

For external MCP hosts, the runtime exposes the server over stdio and HTTP. The architecture may use a local WebSocket connection when an external host must control a Viewer running in a browser. That connection is not needed for the hosted browser demo or for integrations that execute directly inside the web application.

The bridge is described as supporting more than 60 commands. The WebMCP adapter exposes 61 browser-safe commands arranged into 12 selectable toolsets, and its example can automatically route requests among toolsets while limiting the number of tools presented for a normal request.

## Setup and configuration

The quickest evaluation path is the hosted browser-agent demo, which requires no installation or signup. For a local WebMCP example, the repository documents building the bridge and WebMCP packages, serving the project directory, and opening the browser-agent example. WebMCP testing requires a compatible experimental browser configuration; the README specifically identifies Chrome 149+ and browser flags for local testing.

Application developers can install `cesium-mcp-webmcp` and register a Cesium Viewer with the adapter. The registration supports selecting toolsets and excluding tools, such as omitting the built-in geocoder when an application supplies its own. End users of an integrated website do not need to install npm packages or run an MCP server.

To connect an external MCP host, install and run the `cesium-mcp-runtime` package. The repository identifies Claude Desktop, Cursor, and Dify as runtime consumers, although this listing only covers client compatibility where supported by the directory schema. No API key or environment variable is specified in the provided material.

## Tools and capabilities

The gaopengbin/cesium-mcp MCP server is suitable for agents that need to:

- Move or fly the Cesium camera to a requested location.
- Add or manage GeoJSON and 3D Tiles content.
- Place markers on the globe.
- Perform supported spatial analysis operations.
- Generate or control heatmap visualizations.
- Discover Cesium browser tools through WebMCP.
- Invoke the same Cesium command layer through MCP, function calling, or browser-agent integrations.

The shared contracts package keeps tool descriptions and schemas transport-neutral. This allows the browser and MCP adapters to expose related commands without requiring separate Cesium implementations for each protocol.

## Limitations and notes

This project controls a CesiumJS Viewer; it is not presented as a general geospatial database, hosted map service, or standalone desktop globe. The MCP runtime is only necessary when an external MCP host must reach a live browser Viewer. Browser-agent, WebMCP, and function-calling paths can execute commands in the web application without a backend MCP server.

The WebMCP path depends on browser support for `document.modelContext` and is described as experimental in the setup guidance. The live demo uses a hosted model and does not require a browser API key, but the provided material does not define authentication, deployment requirements for every integration path, or the full schema of each command. The gaopengbin/cesium-mcp MCP server is released under the MIT license.

_Full upstream README: https://allmcps.com/mcp/gaopengbin-cesium-mcp/readme_