Skip to main content
The DataGalaxy app provides full read/write access to the DataGalaxy data catalog API. It can be used either as a Builder app (automations call DataGalaxy instructions directly) or as a remote MCP server consumed by an Knowledges agent.

Catalog Management

Sources, containers, structures, fields, glossary, usages, data processing

Links & Collaboration

Relationships, comments and tasks across any catalog entity

Dual Interface

Use as Builder app or MCP server exposed to agents

Prerequisites

  • A DataGalaxy account with API access
  • A Personal Access Token (PAT) or integration token
  • The DataGalaxy API base URL (default: https://api.datagalaxy.com)

Installation

  1. Go to Apps in your workspace
  2. Search for DataGalaxy and install it
  3. Open the app instance configuration and fill in the required fields

Configuration

MCP Endpoint and MCP API Key are generated automatically by the onInstall flow and are only needed if you intend to expose this instance as an MCP server (see the next tab).

Available Instructions

Every instruction resolves credentials from the workspace configuration via buildAppAuth. Unless stated otherwise, all IDs use DataGalaxy’s DoubleUuid format and versionId refers to a workspace version ID returned by listVersions.

Search & Workspaces

Generic Object Operations

status accepts Proposed, InRevision, Validated, InValidation, Obsolete.

Sources

Containers

type accepts Model, Directory, Equipment.

Structures

type accepts Table, Document, File, SubStructure, Tag, View.

Fields

type accepts Column, Field. columnDataType is free-form (e.g. varchar, int, date).

Glossary Properties

type accepts Universe, BusinessDomain, BusinessDomainGroup, ReferenceData, ReferenceDataValue, Dimension, DimensionGroup, Concept, Indicator, IndicatorGroup, BusinessTerm.

Usages

type accepts Application, Algorithm, Dashboard, Feature, DataSet, OpenDataSet, Screen, Process, Report, Usage, UsageField, UsageComponent.

Data Processing

type accepts DataFlow, DataProcessing.

Comments

Tasks

DSUL Examples

Search the Catalog

List Workspaces and Versions

Create a Source

Create a Structure and a Field


Error Handling

Common Issues

“Not configured” — No credentials could be resolved. Either complete the app install with a valid token, pass an Authorization: Bearer header, or call configureDataGalaxy before the first tool call. “Invalid API key” — The mcp-api-key header does not match the central app secret. Reinstall the app instance to regenerate a signed key. “Credentials lookup failed” — The MCP endpoint could not reach the getConfig webhook of the installed app. Verify that the app instance is still installed in the expected workspace.

External Resources

DataGalaxy API

Official DataGalaxy API documentation

Tool Agents

Plug MCP servers into Knowledges agents