Who it is forAn analyst who thinks in SQL but needs Python for the rest of the analysis.
The problemSwitching between a SQL client and a notebook breaks the flow and loses reproducibility.
The outcomeA notebook where SQL results come back as Python dataframes and the whole thing is still a .py file.
What you need first
- Python and pip or conda
- Optional: marimo[recommended] for SQL cells, AI completion and more
- Optional: your own API keys or a local model for AI features
Steps
- Install the extras that unlock SQL cells with
pip install "marimo[recommended]" - Open a notebook with Marimo edit and add a SQL cell that references a Python variable
- Query dataframes, databases, CSVs or warehouses with the built-in SQL engine
- Page through, search, filter and sort the result in the interactive dataframe viewer
- Run pytest on the notebook if you want tests around the analysis
Prompt for your agent
Using marimo-team/marimo, create a notebook that loads <CSV or database>, adds a SQL cell filtered by a Python dropdown value, and shows the result in an interactive dataframe.
Caveat. This card is written from the marimo-team/marimo README, not from a test run by Deduped. Before you start, make sure you have Python and pip or conda. Check the repo for newer instructions before you rely on these steps.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for marimo-team/marimo and "Query dataframes and databases with SQL in Python notebooks"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer