
Gretl MCP
Drive Gretl econometrics scripts from your agent, capture run artifacts, and optionally open the Gretl GUI for inspection.
Overview
Gretl MCP is a Build-phase MCP server that runs Hansl/Gretl econometrics workflows, manages artifact workspaces, and can launch the Gretl GUI from agent sessions.
What is this MCP server?
- Runs Hansl/Gretl econometrics workflows via MCP stdio npm package gretl-mcp v0.2.1
- Optional visible Gretl GUI launch; GRETLMCP_OPEN_GUI=false to suppress
- Workspace dir via GRETLMCP_WORKSPACE_DIR for runs and generated artifacts
- Override paths with GRETL_CLI and GRETL_GUI env vars
- Artifacts from runs usable in downstream reporting or validation
- Server version 0.2.1
- npm package identifier gretl-mcp
- 4 documented environment variables for CLI, GUI, workspace, and GUI toggle
Community signal: 3 GitHub stars.
What problem does it solve?
Econometrics work in Gretl stays outside your agent loop, so you copy scripts and results by hand.
Who is it for?
Solo analysts or technical founders who use Gretl for models and want Claude/Cursor to orchestrate repeatable Hansl jobs.
Skip if: Builders with no Gretl install who only need generic Python stats or spreadsheet MCP tools.
What do I get? / Deliverables
Your agent can trigger Gretl runs, store artifacts in a configured workspace, and optionally open Gretl for visual follow-up.
- Executed Gretl/Hansl workflow outputs in a workspace
- Optional GUI session for model inspection
- Agent-callable econometrics runs without manual CLI copy-paste
Recommended MCP Servers
Journey fit
How it compares
Specialized Gretl/Hansl MCP bridge, not a general dataframe or BI connector.
Common Questions / FAQ
Who is Gretl MCP for?
Developers and researchers already using Gretl who want MCP agents to run scripts and collect econometric outputs.
When should I use Gretl MCP?
When validating pricing models, demand forecasts, or experiment analysis that lives in Gretl and should be agent-triggered.
How do I add Gretl MCP to my agent?
Install gretl-mcp from npm, point env vars at gretlcli/gretl GUI if needed, set GRETLMCP_WORKSPACE_DIR, and register the stdio server in MCP config.