Data API Builder — REST/GraphQL + MCP Tools

Practical Notes

• GitHub: 1,404 stars · 337 forks; pushed 2026-05-12 (verified via GitHub API).
• README installs the CLI via dotnet tool install ... -g, then uses dab init, dab add, and dab start for a working API.
• README notes REST + GraphQL defaults, plus endpoints like /health, /swagger, and /graphql for local validation.

Main

What makes DAB useful for agents is structure:

• Put your connection string in env vars and keep .env out of git.
• Keep your dab-config.json under version control so changes are reviewed.
• Start with least-privilege permissions (even in examples) and expand only when your API surface is stable.

Once the API is stable, you can let an agent generate client code or queries against the REST/GraphQL endpoints without giving it raw DB credentials.

FAQ

Q: Do I need containers? A: Not for development—README runs locally with dab start; production commonly uses containers.

Q: Is the config required? A: Yes—README says DAB requires a JSON configuration file and generates dab-config.json.

Q: How should I secure it? A: Use env vars for secrets, version control configs, and keep permissions least-privilege by default.