Claude Starburst connectorWhat Claude can do in your Starburst account.
The Claude Starburst connector exposes 1 tool, and it reads. 0 write tools, 0 undocumented ones. Below: what Claude can query across your Galaxy catalogs, the setup Starburst needs first, and where the connector stops for good.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you query Starburst from Claude
You no longer open the Galaxy query editor and dig for the right schema name. You ask Claude a question in plain English, it writes the SQL itself, runs it read-only against your Starburst catalogs, and hands back a compact result right in the chat, within your role.
Get your bearings in an unfamiliar warehouse. Starburst lists data exploration as the first use case: through readOnlyQuery, Claude walks the schemas and the way catalogs are organised, so you learn where things live.
Pull a number without writing SQL. Ask for an analysis or a quick report in everyday words; the tool runs an analytical query over the catalogs your role can reach, under the timeouts and result-size caps Starburst already enforces.
Look at a few rows before going further. The publisher also describes lightweight sampling: the same tool returns a short extract of the data, within the result-size limit Starburst sets, so you see what a table holds before asking for an analysis.
What it won't do: Starburst restricts the server to read statements (SELECT, SHOW, EXPLAIN), so inserting, updating, deleting or creating tables is refused. Claude sees only what your default Galaxy role allows, and a custom role can't be picked. Nothing runs on its own either, no query fires on a schedule or when data lands. That kind of background job is an automation tool's work, a different trade; the Integrations hub covers that side.
The vocabulary in one minute
Five words you'll meet while connecting Starburst.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named action a connector opens up to Claude. Claude picks the ones it needs by itself, and the directory sheet lists every tool by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service in the first place.
Connect Starburst to Claude in three steps
- 01
Find Starburst in Claude
In Claude's settings, open Customize, then Connectors, and look for Starburst in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first, before each member can sign in on their own.
- 02
Start the connection
Click Connect on its row, then sign in to Starburst Galaxy in the window the service opens itself. If the link ever breaks, use Disconnect and connect it again from the same row.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Starburst, not Claude, and it decides what the access covers. Whatever you grant there can later be withdrawn from your Galaxy account as well.
The single tool in the Claude Starburst connector
Starburst gives Claude 1 tool: 1 that read your account, 0 that change something in it.
One tool, filed on the reading side. Its name stays exactly as Claude shows it.
- 1 read
What Claude reads (1)
1 toolOne tool that queries your catalogs without changing them.
readOnlyQuery
Runs a read-only SQL query against the Starburst catalogs you can reach and returns a compact, structured result into the conversation. It covers data discovery, light sampling and analytical queries alike.
What Claude asks you before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. Here, the only tool just reads.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time. They can also cap what a connector may do across the organisation, and nobody overrides that from their own account. On the Starburst side, Claude inherits the default role of whoever connected: a catalog closed to that role stays closed to Claude, whatever the wording of your request.
Which plans it's available on
None of the 819 sheets in the official directory shows availability by plan. For Starburst as for every other connector, that answer isn't published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organisation before members can connect. For the current state, check the connector's sheet in the directory.
Where this connector stops
A connector isn't an automation: Claude calls its tool while it answers you, and nothing kicks off when a table changes. Only the publisher documents this connector.
By default the sheet shows only reading, and that is an observed floor rather than a promise: an administrator can open actions no public sheet lists. The directory's partner badge isn't a security audit either, and Anthropic says so on every sheet: it doesn't choose a publisher's tools or vouch for how they behave. Connect only what comes from a publisher you know, here Starburst Data, and read its documentation before you connect. Other connectors are gathered on the Claude integrations page.
Need help connecting Starburst to Claude?
A person reads every message.
