Extend and integrate
Build a database provider, embed published Go packages, reuse Ptah components, or connect an AI client through MCP.
The CLI is one adapter over Ptah’s schema, planning, rendering, and migration packages. Build a separate provider to add a database engine, embed the published Go surface in a program, or expose a constrained command surface to an AI client.
Common tasks
Section titled “Common tasks”Choose the boundary
Section titled “Choose the boundary”Use a provider when Ptah must read, plan, and change an engine it does not ship. Use Go packages when your program owns types, control flow, and error handling. Use MCP when an external client needs discoverable tools under a restricted policy. Use AI assist when the desired result is a command suggestion for a human to inspect rather than a callable tool.
Anything under internal/ can change without preserving an import contract.
The public API ledger is the authority on supported packages.
Reference
Section titled “Reference”Native command reference includes the MCP server and tool inventory generated from the current command tree.