D3 MCP Server

A star map with D3.js. That is what the d3 mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Interactive, adaptable celestial map done with the D3.js visualization library. So, GeoJSON for sky stuff. Which surprisingly nobody has done yet, it seems.

The tools it exposes

The server publishes 3 tools. What each one is for:

• Usage — // Display map with the configuration above or any subset thereof Celestial.display(config);
• Animations — Animation sequence format: [ {param: Animated parameter projection|center|zoom value: Adequate value for each parameter duration: in
• HowTo — First of all, whatever you add needs to be valid geoJSON. The v

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. D3's toolset — Usage, Animations, HowTo — is a fair guide to whether it matches your workflow. It is maintained by ofrohn; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against D3's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.