data-api-builder-multisource

Configure a single Data API Builder instance to serve multiple databases.

1|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/JerryNixon/vslive-2026-las-demos --skill data-api-builder-multisource
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-api-builder-multisource
Source: https://github.com/JerryNixon/vslive-2026-las-demos/tree/main/.github/skills/data-api-builder-multisource
Command: npx skills add https://github.com/JerryNixon/vslive-2026-las-demos --skill data-api-builder-multisource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure a single Data API Builder (DAB) instance to serve multiple databases by partitioning configs into a parent and per-database child configs, merging all entities into a unified API surface without code.

Core Features & Use Cases

  • Single DAB instance serving REST, GraphQL, and MCP across multiple databases.
  • Separate child configs per database containing their own data-source and entities, with a merged API surface.
  • GraphQL can query across databases; REST and MCP expose entities from all sources in a unified namespace.
  • Uses environment variables for per-database connections and supports mixing database types.

Quick Start

Create a parent dab-config.json listing all child configs via data-source-files, add per-database dab-config-*.json files, supply the required environment variables, and start DAB to expose multi-database APIs.

Frequently Asked Questions about data-api-builder-multisource

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a single Data API Builder instance to serve multiple databases?▼

To serve multiple databases, configure a single Data API Builder instance by partitioning configs into a parent file listing child configs via data-source-files, and per-database child configs containing their own data-source and entities.

Can I expose unified REST, GraphQL, and MCP endpoints across different databases without writing code?▼

Yes, you can expose unified REST, GraphQL, and MCP endpoints across multiple databases without code by merging child config entities into a single API surface through a parent Data API Builder configuration.

How do I split Data API Builder configs across files for multi-source database connections?▼

You split Data API Builder configs by creating a parent dab-config file with runtime and data-source-files properties, then creating separate per-database child dab-config files containing their specific data-source and entities.

Does Data API Builder support querying across multiple databases using GraphQL?▼

Yes, Data API Builder supports GraphQL queries across multiple databases. REST and MCP also expose entities from all configured data sources within a unified namespace.

Do I need environment variables to connect Data API Builder to multiple database sources?▼

Yes, you need environment variables for per-database connections. The multi-source configuration requires that environment variables resolve correctly for all parent and child configs to successfully start the API.

Can I mix different database types in one Data API Builder multi-source configuration?▼

Yes, you can mix different database types in one Data API Builder configuration. Separate child configs per database allow you to support various database types while exposing a merged API surface.