Nucleus Studio
One visual surface for all 14 Nucleus data models. SQL tables, graph explorers, vector visualizers, time-series charts, document browsers — no more switching between pgAdmin, Neo4j Browser, and a Redis CLI.
See your data. All fourteen models.
One window for every data model.
Nucleus supports fourteen data models in a single engine. Studio gives each one a real UI: tables for SQL, force-directed graphs for edges, scatter plots for embeddings, charts for time-series, key browsers for KV, map views for geo. Connect once, browse everything — no switching apps, no re-entering credentials.
Ships with an MCP server.
Studio includes a built-in MCP server with 17 tools for LLM clients — schema introspection, query execution, index recommendations, migration generation. Point Claude Desktop at it and your LLM can browse and reason over your database without an integration layer.
{
"mcpServers": {
"nucleus": {
"command": "neutron",
"args": ["studio", "--mcp", "--stdio"]
}
}
}Built with Neutron
Studio is a Preact + signals SPA served by a Go embedded server (shared with the CLI) that talks to Nucleus. It's the reference proof that the Neutron stack handles a real, complex app — file-based routing, typed loaders, islands for interactive panels, and the same pgwire client every other Neutron SDK uses.
How to run it
neutron studio from any project, or neutron studio --url postgres://host/db pointed at any Nucleus instance. Opens at http://localhost:7000 by default.
Part of a bigger system
Studio is the visual counterpart to the CLI, the SDK clients, and the MCP server. Whatever language writes to Nucleus, Studio can browse it. Whatever LLM you connect to MCP, it reasons over the same schema Studio is showing you.