Metabase vs Cesium MCP

A side-by-side look at the Metabase and Cesium MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Metabase logoMetabaseData VisualizationLets AI clients search, explore, query, and visualize data in a Metabase instance.41FairAuth: not declaredCesium MCP logoCesium MCPData Visualization · Local subprocess (stdio)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.69GreatAuth: no auth required

Verdict: choose Metabase for data visualization work; choose Cesium MCP for data visualization as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Metabase logoChoose Metabase when

  • You need dedicated capabilities in the Data Visualization domain.
Explore Metabase

Cesium MCP logoChoose Cesium MCP when

  • You need dedicated capabilities in the Data Visualization domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like flyTo, setView, getView.
Explore Cesium MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMetabase logoMetabaseCesium MCP logoCesium MCP
CategoryData VisualizationData Visualization
Quality signal41/100 · Fair69/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars49,815145
Directory activity 1 views 0 installs 0 upvotes 9 views 0 installs 0 upvotes
ToolsNot listed33

Tools & capabilities

Metabase tools

No tool names declared yet. Check the project README from the listing page.

Cesium MCP tools 33

  • flyToAnimate the camera to a geographic location. Use for visible navigation requested by the user. Returns { success: boolean, message?: string, error?: string }.
  • setViewSet the camera position immediately without animation. Use for deterministic setup or instant view changes. Returns { success: boolean, message?: string, error?: string }.
  • getViewGet the current camera position and orientation. Returns { success, data: { longitude, latitude, height, heading, pitch, roll }, message? }.
  • zoomToExtentAnimate the camera to a west/south/east/north bounding box. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • saveViewpointSave the current camera state under a page-local name. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • loadViewpointRestore a previously saved page-local camera state. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • listViewpointsList camera viewpoints saved in the current page. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • exportSceneExport the current view, layer, and entity state as JSON. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • addMarkerAdd a point marker at geographic coordinates. Returns { success, data: { entityId }, message? }; keep entityId for removeEntity.
  • addLabelAdd property-based text labels for GeoJSON features. Returns { success, data: { labelCount: integer }, message? }.
  • addModelAdd a glTF or GLB model at geographic coordinates. Returns { success: boolean, data?: unknown, message?: string, error?: string }.
  • addPolygonDraw a polygon area from geographic coordinate tuples. Returns { success, data: { entityId }, message? }; keep entityId for removeEntity.
  • +21 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Metabase

No confirmed install command for Metabase yet — follow the setup steps linked from its listing page rather than a guessed package name.

Cesium MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gaopengbin-cesium-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cesium-mcp-runtime"
      ]
    }
  }
}

Frequently asked questions

Metabase is categorized under Data Visualization and uses an install path we have not confirmed yet. Cesium MCP belongs to Data Visualization and uses a local stdio subprocess. Pick Metabase for data visualization work and Cesium MCP for data visualization.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Metabase has no confirmed install command yet — follow its own setup instructions.

Metabase is listed as free. Cesium MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add metabase and gaopengbin-cesium-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Metabase has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 49,815 GitHub stars. Cesium MCP has 69/100 (Great) with 9 views, 0 installs and 145 GitHub stars.