Dough Docs
Use Dough from AI clients through MCP, typed tools, data lake tables, and the team filesystem.
What Dough exposes
Dough publishes one typed tool registry across the web app, MCP clients, the local CLI, and sandboxed TypeScript. Agents can discover tools, inspect schemas, and compose finance workflows without a transport-specific action schema.
The core surfaces are data lake tables read through integrations.*, and a DB-backed team filesystem. All organization-scoped tools default to the current WorkOS organization when one is available, and to default in local development.
- Connect AI clients through
/api/mcpusing Streamable HTTP and OAuth. - Discover tools with
tools.listand inspect one tool at a time withtools.describe. - Read synced source data through
integrations.*, and work with organization files throughfiles.*andunix.*. - Use
/llms.txtfor an LLM-readable version of these docs.
LLM-readable docs
/llms.txt renders the same docs registry as plain text. Point coding agents, custom GPT instructions, or MCP client context loaders at that URL when they need a compact reference without scraping the UI.