Causal Inference Tooling
A DAG editor for a web browser, and an MCP server for AI agents, built for pharmacoepidemiology and real-world evidence.
What's Inside
A drag-and-drop editor and a Model Context Protocol server, sharing one identification engine. Each can be used on its own.
Surface 01
A drag-and-drop DAG editor with an in-browser causal-inference engine. Backdoor paths, adjustment sets, identifiability checks. No install required.
Surface 02
The same engine exposed as a Model Context Protocol server. AI assistants can query identifiability, suggest adjustment sets, and flag overadjustment, with citations.
The Editor
The MCP Server
Alongside the editor, DAG Studio also runs as a Model Context Protocol (MCP) server. Where the AI DAG Assistant drafts a starting diagram for you to refine, the MCP server does something complementary: it lets an AI assistant query a real causal-inference engine while you reason about study design, checking identifiability, suggesting adjustment sets, and flagging overadjustment, rather than hallucinating about d-separation. The AI proposes; the engine verifies.
Tool surface (v1)
Request a trial token, then point any client or API that supports remote MCP at https://dagstudio-mcp.blackswancausallabs.com/mcp. That includes Claude.ai connectors, Claude Code, ChatGPT (Business or Enterprise, developer mode), and the OpenAI and Anthropic APIs as a remote MCP tool. Request access →
Release History
| Version | Date | Highlights |
|---|---|---|
| v2.0Current | Jul 2026 | AI DAG Assistant that drafts a causal diagram from a plain-language research question, radial layout for generated DAGs, new About and FAQ sections, and console and canvas usability improvements. |
| v1.0 | 2026 | Initial release: drag-and-drop editor, in-browser identification engine, bilingual Python and R console, linear Gaussian SEM data simulation, and the education library. |
Get Involved
DAG Studio's source is provided to pilot partners and reviewers on request, under the MIT license. Inspectable tooling is the right shape for software that may inform regulatory submissions: the engine should not be a black box to the teams and reviewers who rely on it, even though the repository itself is private.
If your team is considering integrating DAG Studio into protocol development workflows, a small pilot program is open. Pilot scope: two protocols, four weeks, written feedback in exchange for early access and direct engine support. Pharmacoepidemiology and real-world evidence teams are the primary audience.