M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
W

WorldWideView

Community
Open-source, plugin-driven geospatial intelligence engine
How to install ↓ Compare GitHub source repository ↗
Category
Other #179 of 230
Stars
★ 1.9k Very popular
Transport
Streamable HTTP
Runtime
Node.js 18+ · Docker · Hosted (no local runtime)
Credentials
API key / credential required
License
Other / unspecified
Last commit
45FMRS · D

WorldWideView offers a unique MCP server for controlling a live globe visualization, but its tool set is underdocumented. It suits developers interested in geospatial AI integration but requires API key management and plugin loading awareness.

Strongest · Documentation 12/20 Weakest · Reliability 5/20

Reliability
5/20
Security and permissions
10/20
Maintenance
10/20
Documentation
12/20
Setup experience
8/20
Why each score
Reliability 5/20
The repository is primarily a frontend geospatial rendering engine, not a dedicated MCP server. The README claims a built-in MCP endpoint (/api/mcp) and agent bus, but no source code or tests for these components were provided in the static review. No CI configuration or test files were found to verify MCP handshake or tool listing. Thus, while implementation may be plausible, reliability cannot be confirmed from source.
Security and permissions 10/20
The README describes API-key-based Bearer token authentication, which is a relatively secure approach. No obvious malicious code or credential leaks were found. However, the permission model and request validation specifics were not reviewed from source, so security score is limited. No red lines detected, and install examples contain no real tokens.
Maintenance 10/20
The repository has recent commits, CI badges, and release workflow, indicating active maintenance. However, the license is NOASSERTION (despite README claiming Elastic 2.0), which limits the maintenance score. Lack of clear governance or security response channels, but overall active.
Documentation 12/20
The README is very detailed, covering installation, configuration, example MCP client config, and mentions authentication and dynamic plugin tool catalogs. However, troubleshooting and detailed tool parameter descriptions are missing. Documentation about MCP endpoint internals relies on source code that was not provided. Thus, documentation balances usability and depth.
Setup experience 8/20
Self-hosting scripts provide one-shot setup, and MCP config examples target mainstream clients. But it requires running the whole Next.js app including a database, adding complexity. Static review provides no executable evidence, and installation steps' reliability cannot be verified.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkControls a browser

Best for

  • Developers building AI-driven situational awareness tools or geospatial data exploration.
  • Teams looking to add MCP control to a CesiumJS-based platform.

Not for

  • Users expecting a rich set of MCP tools (none are documented currently).
  • Users wanting a simple integration without managing API keys or configuration.

Required permissions

  • Access to the WorldWideView instance (requires API key).
  • Potentially control the browser session (via optional Agent Bus).

Risks and side effects

  • The server is stateless and cannot push list_changed notifications proactively; clients may need to refetch.
  • Plugin tools appear only after the corresponding plugin is loaded.
  • Bearer token exposure if shared insecurely.

Setup

Before you start

Runtime：Node.js 18+ · Docker · Hosted (no local runtime)

DATABASE_URL required PostgreSQL connection string, required for production deployments via Prisma.
AUTH_SECRET optionalsecret Authentication secret auto-generated into .env.local by pnpm run setup for local development.

Generate an API key from the /setup page of your running WorldWideView instance. Then add the following configuration to your MCP client (replace https://your-host with the actual origin): { "mcpServers": { "worldwideview": { "type": "http", "url": "https://your-host/api/mcp", "headers": { "Authorization": "Bearer <your-api-key>" } } } }

claude_desktop_config.json 
{
  "mcpServers": {
    "worldwideview": {
      "type": "http",
      "url": "https://your-host/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "worldwideview": {
      "type": "http",
      "url": "https://your-host/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add --transport http worldwideview https://your-host/api/mcp --header 'Authorization: Bearer <your-api-key>'

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Generate an API key on the /setup page, connect your MCP client to https://your-host/api/mcp, then call tools/list — it should return the tools exposed by the running instance (including plugin-published tools). Plugin tools only appear after the browser tab running WorldWideView has loaded them; call tools/list again after loading new plugins.

Troubleshooting

  1. Ensure the API key is correctly passed as a Bearer token.
  2. If plugin tools don't appear, reload tools/list after loading the plugin in the browser.
  3. Verify the WorldWideView instance is reachable from the MCP client (correct URL and network).

Things to try

Once connected, you can ask your AI assistant things like:

  • List the tools available in this WorldWideView session
  • Toggle a data layer on the running globe
  • Select an entity on the globe and describe it

Use cases

Control a live 3D globe in real-time from an LLM agent for situational awareness.
Visualize real-time aircraft, maritime, or event data in an interactive global environment.

Supported clients

Claude Desktop
Claude Code
Cursor
Cline

Listed from the project's documentation, not tested by this site.

Overview

WorldWideView is a real-time geospatial engine that visualizes live global data on an interactive 3D globe. Using a dynamic 'All-Bundle' plugin architecture, independent data sources—like live aircraft, maritime vessels, or conflict events—are ingested and rendered decoupled from the core 3D viewer. The platform includes a built-in MCP endpoint (/api/mcp) that allows MCP clients (e.g., Claude Desktop, Cursor) to connect directly with Bearer token authentication. The server also exposes an optional Agent Bus (HTTP+SSE control surface) for external tools to drive the running browser session.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →
Compare with other MCP servers

Source revision 33df7a5b7f89 Data synced 2026-10-19 Read the FMRS scoring method