Working with Marimo

Follows a Plan-Execute-Verify loop to ensure notebook correctness.

Feedback Loop

1. Context & Plan:

Sessions: mcpmarimogetactivenotebooks (Find session IDs). Structure: mcpmarimogetlightweightcellmap (See cell IDs/content). Data State: mcpmarimogettablesandvariables (Inspect DataFrames/Variables). Cell Detail: mcpmarimogetcellruntime_data (Code, errors, local vars).

1. Execute:

Edit the .py file directly using write or searchreplace. Rule: Follow [Best Practices](reference/bestpractices.md) (e.g., @app.cell, no global state).

1. Verify (CRITICAL):

Lint: mcpmarimolintnotebook (Static analysis). Runtime Errors: mcpmarimogetnotebookerrors (Execution errors). * Outputs: mcpmarimogetcell_outputs (Visuals/Console).

Common Commands

• Start/Sync: Marimo automatically syncs file changes.
• SQL: Use mo.sql for DuckDB queries.
• Plots: Use plt.gca() or return figure. No plt.show().

Reference

See [Best Practices](reference/best_practices.md) for code formatting, reactivity rules, and UI element usage.