USER GUIDE
Get started with Dolex
Connect Dolex to Claude, point it at your CSV files or a live Postgres/MongoDB database, and get expert-level visualizations in minutes. This guide walks you through setup and your first analysis.
Install Dolex
Install Dolex globally with npm:
npm install -g @outsidedata/dolexThis installs the dolex command globally. Next, you'll point Claude at it.
Connect to Claude Code
Dolex runs as an MCP server that Claude Code connects to over stdio. You register it once and it's available in every conversation.
Add to your MCP config
Open your Claude Code MCP settings and add Dolex as a server. The exact config depends on your setup:
{
"mcpServers": {
"dolex": {
"command": "dolex"
}
}
}Note
If you use nvm or a version manager, you may need a shell wrapper to set the right Node path. See the Docs for details.
Verify the connection
Once configured, you can verify Dolex is running by asking Claude:
What visualization tools do you have available?
I have access to Dolex, a data-analysis tool with 43 chart types across 7 categories. I can connect to your CSV files, a Postgres database, or MongoDB, then profile the data, audit its quality, and build charts and full analysis plans.
Your first chart
The fastest way to see Dolex in action is to point it at a CSV file on your machine. Tell Claude to load it, then ask a question about the data.
Load ~/data/sales-2024.csv and show me which regions are performing best.
I'll load that CSV with Dolex. Found 4 columns (region, quarter, revenue, units) across 500,000 rows. For comparing trajectories across quarters, Dolex returns a slope chart showing how each region's path moves over time.
Note
Your CSV files must be on your local machine — Dolex reads them from disk via file paths. You can't drag a file into Claude's chat window and have Dolex pick it up. Instead, give Claude a path like ~/data/sales.csv and tell it to use load_source. Dolex runs locally as an MCP server with full filesystem access, so the path gets resolved server-side on your machine.
Dolex's pattern selector reads the data shape and your comparison intent, then matches a chart type to the story in the data — in this case, the crossing trajectories a slope chart makes visible.
Force a specific chart type
If you want a specific chart type, just ask for it by name. Dolex has 43 chart types — far beyond bar, line, and pie:
Explore a dataset automatically
This is where Dolex really shines. Instead of asking one question at a time, you can hand it a dataset and let Dolex figure out what's interesting. It examines every column, understands what each one represents, and generates a full analysis plan.
How to use it
Just ask Claude to explore your data. It will load the CSV, call the analysis planner, and execute each recommended visualization with a narrative finding. The output looks like a data analyst sat with you and walked through the dataset.
Load ~/data/sales-2024.csv and explore what's interestingWhat the planner does
The planner examines column profiles and generates 4–6 analyses, each with a ready-to-execute query. It picks from these categories:
Monthly revenue over time
line, area, sparkline grid
Revenue by region
bar, lollipop, diverging bar
Spread of order values
histogram, violin, beeswarm
Price vs. quantity correlation
scatter, heatmap
Top 15 products by sales
bar, lollipop
Revenue share by category
treemap, sunburst, donut
The planner diversifies — it won't produce two trend charts or two comparisons. Each step covers a different analytical angle.
Manual approach
If you prefer to drive the analysis yourself, you can load a CSV and call the planner separately:
Load ~/data/sales.csv, then analyze it and tell me what's interesting.
I'll load this CSV and run Dolex's analysis planner. Based on the column profiles (date, region, product, revenue, quantity), the planner suggests 5 analyses covering trends, comparisons, distribution, ranking, and relationships. Let me execute each one...
Work with your data
For anything beyond small inline datasets, connect a source: a CSV file (or a whole directory of them), a live PostgreSQL database, or MongoDB. Dolex profiles the data and processes it locally — only summaries and chart specs flow through the conversation, not your raw data. Load multiple CSVs and Dolex can automatically combine them by matching columns.
Load a CSV
Tell Claude about your CSV file. Dolex loads it locally so you can ask questions about it without sending your actual data to the AI:
Load ~/data/orders.csv and show me revenue by month for the past year.
Loaded "orders" — found 8 columns across 500,000 rows. I'll query with a monthly revenue aggregation and visualize the trend.
Once loaded, you can ask follow-up questions without reloading. Loaded CSVs persist across conversations:
Now break that down by product category.
I'll add product category as a grouping dimension. With 6 categories across 12 months, Dolex returns a sparkline grid — one mini trend per category so you can compare trajectories at a glance.
Connect a live database
A Postgres or MongoDB database works the same way — Dolex queries it in place, so you never copy the data anywhere. The database drivers are optional; ask Claude to check capabilities first and it will tell you the one command to install a missing one. Credentials stay out of the registry — a Postgres password is read from an environment variable at connect time.
Connect to my Postgres warehouse (host db.internal, database analytics) and show revenue by region.
Registered "warehouse" and profiled the public schema. I'll query the orders table in place and visualize revenue by region — your credentials came from PGPASSWORD, and nothing was copied off the database.
What stays private
Claude sees
- Column names and types
- Summary statistics (min, max, mean)
- Top categorical values
- 5 sample rows
- Chart spec IDs (not raw data)
Stays on your machine
- Your actual data rows
- All data processing
- Query result sets
- The rendered chart HTML
Refine and iterate
Every chart Dolex produces can be refined. Ask for changes naturally — Claude will call the refine tool with no data round-trip (it references the chart by its spec ID).
Things you can change
Switch chart types
Every visualization comes with alternative chart type recommendations. You can switch between them without re-sending data:
Show that as a heatmap instead.
Switching to heatmap. The same data now shows intensity patterns — you can see the Q4 surge is concentrated in the North and East regions.
Color palettes
Dolex ships with purpose-built palettes. Ask by name or by intent:
Tips for better results
State your intent, not just the chart type
Instead of “make a bar chart,” say “compare revenue across regions” or “show how rankings changed over time.” Dolex's pattern selector uses intent keywords to score all 43 chart types — the more context you give, the better the recommendation.
Connect a real source for real datasets
Inline data works for quick demos, but for anything over ~50 rows, give Claude a file path (or a database connection) and let Dolex load it. It's faster (no data in the conversation), more private (data stays local, or on your own database), and unlocks the full query engine — filtering, grouping, sorting, and even combining multiple tables.
Let the planner drive discovery
When you don't know what questions to ask, ask Claude to explore your data or call analyze_data. The planner examines column profiles and generates hypotheses — it finds the time trends, comparisons, and distributions you'd want to see.
Iterate, don't restart
Every chart has a spec ID. When you ask for changes, Dolex references the existing spec — no data re-upload, no re-querying. This makes refinement nearly instant.
Ask for the chart type by name
Dolex has patterns most people have never heard of: ridgeline plots, beeswarm plots, alluvial diagrams, horizon charts. If you know the name, just ask for it. If you don't, describe what you want to see and let the pattern selector figure it out.
Set titles upfront
Include a title and subtitle in your initial request to avoid a refine round-trip. “Show revenue by region, title it Regional Performance Q4” is one tool call instead of two.
Ready to go deeper?
The docs cover every tool, the query engine, compound visualizations, and the full rendering pipeline.