Enable Self-Serve Analytics

Start Here: Is a MotherDuck Server Active?

Use an active remote MotherDuck MCP server or local MotherDuck server to inspect the in-scope database, schema, grain, keys, and relevant metrics. Reuse known context and narrow discovery to the requested work; do not scan the whole workspace by default. Let the actual data model shape the result.

Resolve the target from the request or active context. Ask only if ambiguity materially affects the result. Without a server, use supplied schema and explicit assumptions for planning; do not imply live validation.

Rollout Defaults

• first audience first, not company-wide exposure
• curated dataset before broad access
• Dive or share boundary over raw table dumping
• standard ownership for metric changes
• lightweight metric definitions and owners before inviting more users
• a short root orientation Guide plus shallow domain Guides for definitions that agents cannot infer from schema
• restricted Shares granted to roles; use include patterns for table/view subsets and separate Shares for different audiences

Workflow