kepler-mcp-demo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | Port for /mcp, /ws and /files. | 8765 |
| token | No | Shared secret - the page and MCP clients must present it. Pick a fixed one so the page URL and claude mcp add header stay stable across restarts. | |
| demo-url | No | The page the daemon tells agents/users to open, e.g., a deploy preview URL. | https://kepler.gl/demo |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| harness_statusA | Check the bridge status. Returns whether a kepler.gl demo page is currently connected to this bridge, and which map.* commands the page is serving. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The single tool has a clear, specific purpose.
The single tool name 'harness_status' is clear and there are no other names to compare against, so no inconsistency exists.
One tool is too few for the apparent scope of a kepler.gl bridge that should serve multiple map.* commands. The minimal count severely limits the server's utility.
The server only provides a status check, while the tool description implies a broader set of map.* commands that are not exposed. Agents cannot actually interact with the kepler.gl demo page beyond checking its status.