What depends on the orders table, and who owns it?
DataHub catalogues your data. Memtro searches datasets, dashboards, charts, pipelines, glossary terms, tags and domains, and reads a dataset's owners, tags, terms, domain, deprecation, health and links, its upstream and downstream lineage, and its incidents. When asked and granted, it can raise and resolve incidents, add or remove tags, terms, owners and links, edit column or container descriptions, set or clear a domain, and mark assets deprecated. The token acts as you, so DataHub's own policies decide what it can read and change. Incident assignees are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right DataHub tool, reads what it needs, and answers with the source cited.
These tools change something in DataHub. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once DataHub is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What depends on the orders table in DataHub?
Who owns the customer_events dataset?
Which datasets are tagged PII in the finance domain?
Are there any active incidents on the revenue dashboard?
Mark the legacy_orders table deprecated with a note to use orders instead.
Dan Fletcher, an analytics engineer at BigCo, asked what would break if he changed the orders table. Memtro read its downstream lineage and listed the dashboards and pipelines that depend on it, with how many hops away each was.
Priya Sharma, a data steward at Acme Ltd, asked Memtro to raise an incident on the customer_events dataset after a late load. Memtro raised it, and the dataset showed as unhealthy to everyone viewing it and its downstream users.
The teams that lean on DataHub most, a question each of them asks, and what they connect beside it.
A record in DataHub is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Grist
NocoDB
Typesense
Weaviate
Tinybird
Hightouch
Census
kintone
Monte Carlo
OpenMetadata
Secoda
Softr
Teable
VectaraIn DataHub, open Settings → Access Tokens and generate a token with an expiry. Your account needs the Generate Personal Access Tokens privilege, and Metadata Service Authentication must be on.
In Memtro, open Connections → DataHub and paste the Personal access token and the DataHub host, without https://.
A service user with read policies, plus edit policies only for the actions you want, is the safer token. An administrator grants the incident and deprecation actions by name to the teams that may use them.
Ask what depends on the orders table in DataHub.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The DataHub tools are the same everywhere.
Only when you ask, and only what it has been granted: raise an incident on a data asset; change an incident's state or stage (for example resolve it); add a tag to an asset or column; remove a tag from an asset or column; add a glossary term to an asset or column; remove a glossary term from an asset or column; add an owner to an asset; remove an owner from an asset; add a link to an asset; remove a link from an asset; edit the description of a dataset column or a container; set an asset's domain; clear an asset's domain; mark an asset deprecated, or not. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Personal access token and DataHub host. In DataHub, open Settings → Access Tokens and generate a token with an expiry. Your account needs the Generate Personal Access Tokens privilege, and Metadata Service Authentication must be on.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
