DbGate Central :: DbGate

Connecting to API Endpoints

Mon, 01 Jan 0001 00:00:00 +0000

DbGate Central connects to three families of API endpoints, using the same New Connection dialog for all of them. Supported endpoint types GraphQL - introspect the schema, browse types and run queries against any GraphQL API. oData - work with oData V4 services as if they were ordinary tables. Shopify - connect to your store through the Shopify Admin API and explore products, orders, customers, metafields and more. Creating a connection Open the New Connection dialog, pick the connection type, enter the service URL, and choose how to authenticate:

Querying GraphQL APIs

Mon, 01 Jan 0001 00:00:00 +0000

Point DbGate Central at any GraphQL API and it discovers what is available for you - no need to dig through separate documentation. Explore the schema DbGate Central introspects the GraphQL schema as soon as you connect. Browse the available types and fields in the tree, then open a query tab to start working. Run queries Write queries with the GraphQL editor and run them against the live API. Supply query variables alongside the query, either in a form or as raw JSON. Results come back in the same fast, sortable, filterable grid used everywhere in DbGate, so a GraphQL response feels like a database table. Nested objects and lists are returned as structured JSON you can expand and inspect in place. Queried views are cached per connection, so reopening them is instant while you keep working.

Browsing and Editing Data

Mon, 01 Jan 0001 00:00:00 +0000

Work with oData services and other endpoints as if they were ordinary database tables - browse, edit, filter and sort results in a fast, spreadsheet-like grid, with no code required. A powerful data grid Filter and sort any column to narrow large result sets in seconds. Edit inline and apply your changes back to the endpoint, with undo/redo while you work. See the shape of your data at a glance with the built-in column value histogram. Export results to CSV, JSON and Excel whenever you need the data elsewhere. The grid is the same engine used across DbGate, so everything you learn here carries over to SQLite, DuckDB and BI reports.

BI Reports from API Data

Mon, 01 Jan 0001 00:00:00 +0000

DbGate Central loads your API responses into its own built-in data engine, so you can combine, aggregate and visualize them - turning raw API responses into readable BI reports. From raw responses to insight Aggregate and pivot your data into summary tables - counts, sums and breakdowns by any dimension. Relate multiple sources so a report can join data that lives behind different endpoints. Drill down through hierarchies to move from the big picture to individual rows. oData and Shopify endpoints (and CSV/JSON/Excel files) can be used as BI sources. GraphQL APIs are great for querying, but are not currently available as a reporting source - browse and query them directly instead (see Querying GraphQL APIs).

MCP Server for AI Agents

Mon, 01 Jan 0001 00:00:00 +0000

DbGate Central can expose your workspace to AI assistants such as Claude as a remote MCP (Model Context Protocol) connector - so an agent can explore and query your APIs the same way you do, with access that you stay in control of. Setting it up Open the Settings tab and create an MCP profile. Copy its Server URL (https://central.dbgate.cloud/mcp/{profileId}), Client ID and Client Secret. In claude.ai (or another MCP-compatible client), add a custom connector using that URL and the OAuth credentials. In each connection’s editor, set its MCP access level - No access, Read-only or Writable. The default is no access, so nothing is shared until you allow it. The assistant runs the OAuth handshake and you consent, binding the connector to that profile and workspace. Each workspace can have multiple MCP profiles, each with its own URL, credentials and per-connection grants. Authentication uses OAuth 2.1 with mandatory PKCE, and client secrets are encrypted at rest.

Connection Proxies

Mon, 01 Jan 0001 00:00:00 +0000

DbGate Central can reach oData and GraphQL APIs that live on a private network by routing their traffic through a small outbound agent that you run inside that network. Shopify and OpenAPI connections cannot be proxied. Setting up a proxy Open the Settings tab and create a proxy under Connection proxies. Copy its generated token. Tick the oData/GraphQL connections the proxy may serve. Each change regenerates the token, so restart the agent after changing the selection. Run the agent inside your private network: npx dbgate-central-proxy --token The agent only makes outbound connections - no inbound access to your network is required. Once the agent is running and connected, requests to the proxied connections are routed through it. If the proxy is not connected, DbGate Central falls back to fetching directly. The same routing also applies to the MCP server: when an MCP tool reads a proxied connection, the request goes through the same proxy.