Install the Claude Code plugin
Install SkaleData's plugin for Claude Code, sign in as yourself, and use the SkaleData MCP gateway and the skills for diagnosing a failed Airflow run and checking the Airbyte sync behind a stale table.
SkaleData's plugin for Claude Code does two things. It configures the SkaleData MCP gateway as an MCP server that signs you in with your SkaleData account, so Claude Code works with your clusters, apps, Superset, Airflow, Airbyte, and DataHub with the same roles you have in the console. And it adds two skills, step-by-step workflows that Claude follows with the gateway's tools:
| Skill | What it does |
|---|---|
/skaledata:airflow-failed-run | Finds the Airflow app, the DAG, the failed run and task, reads the task's log, explains the cause, and, with your approval, clears the failed tasks or triggers the DAG again. |
/skaledata:airbyte-stale-table | Finds the Airbyte connection and stream behind a table, reads the last jobs and their logs, explains why the data is behind, and, with your approval, starts a sync. Secrets stay in the Airbyte UI. |
The plugin's source is at github.com/skaledata/claude-plugin.
Before you begin
- An org admin has turned on MCP data egress for your organization. While it's off, the gateway refuses every tool call. Read What data leaves your cloud first: it explains what reaches your AI provider, which settings control it, and what SkaleData records. See Turn on MCP data egress on this page.
- You've signed in to the SkaleData console at least once with the account you'll use, and you're a member of the organization you'll choose.
- For Superset tools, the app runs the MCP server. Someone with the operator role or higher turns on Run the MCP server in the app's Resources tab.
- For DataHub tools, the app runs the MCP server and checks who you are, and you've opened the DataHub app once from the console. See DataHub tools.
- A Claude Code with plugin support.
/pluginat the prompt opens the plugin manager; if Claude Code says the command is unknown, update it first.
Install the plugin
-
At the Claude Code prompt, add SkaleData's marketplace and install the plugin:
/plugin marketplace add skaledata/claude-plugin /plugin install skaledata@skaledataClaude Code shows what the plugin installs, an MCP server and two skills, and asks for a scope. Choose User to use the plugin in every project, or Project to use it in the current one.
-
Sign in. Run
/mcp, select theskaledataserver, and choose Authenticate. Your browser opens SkaleData's sign-in page: sign in, choose the organization Claude Code acts in, and allow the connection. Claude Code keeps the sign-in in your operating system's credential store, not in a project file, and renews it on its own. -
Check the connection with
/mcp. Theskaledataserver is listed as connected. If it isn't, see Troubleshooting.
From a shell, the same install is claude plugin marketplace add skaledata/claude-plugin and then claude plugin install skaledata@skaledata; the sign-in still happens from /mcp inside Claude Code.
Claude Code identifies itself to SkaleData's sign-in with its published client metadata, so there is no client ID or secret to configure.
Use the skills
Ask in your own words, or name the skill:
- "Why did the
daily_ordersDAG fail this morning?" or/skaledata:airflow-failed-run daily_orders - "Is the sync behind the
orderstable healthy?" or/skaledata:airbyte-stale-table orders
Each skill names the app, the run or job, and the evidence it found before it proposes a change. Each change tool, such as clearing task instances or starting a sync, tells Claude to get your approval first, and SkaleData records the change in the audit log before it's made. What the audit log records lists the fields.
The tools act as you
Because you signed in, every tool runs as you: the skaledata_* tools for clusters, apps, health, deploys, versions, and usage; the Superset tools of each app that runs the MCP server, where the charts and dashboards you create belong to you; the Airflow tools, with your own Airflow role for each app; the Airbyte tools; and the DataHub tools, with your own DataHub permissions. SkaleData's audit log names you for each change. Connect Claude chat to SkaleData describes each tool family and the app settings they need; the same applies in Claude Code.
Headless use with an API key
For CI jobs and other sessions where nobody can sign in, add the gateway to Claude Code with an org-wide API key instead of the plugin's server, as Connect other MCP clients with an API key describes. A key is a shared service identity, not a person: the Airflow, Airbyte, and DataHub tools refuse it, so the two skills stop at their first tool call and say why.
Turn on MCP data egress
MCP data egress is your organization's consent for data to leave for AI clients. It's off for every new organization, and an API key or an AI client can't change it.
- In the SkaleData console, go to Organization > General.
- In MCP data egress, turn on Allow MCP data egress.
Only an org admin signed in to the console can change it. Turning it off refuses the next tool call from every AI client in the organization. See What controls the flow for the other settings that apply, and Turn off MCP data egress to stop all access.
Update or remove the plugin
- To get a new version:
/plugin marketplace update skaledata, and then/plugin update skaledata@skaledata. - To sign out: run
/mcp, select theskaledataserver, and choose Clear authentication. Removing the plugin also drops the connection. - To remove it:
/plugin uninstall skaledata@skaledata.
Troubleshooting
| What you see | What it means | What to do |
|---|---|---|
/mcp shows the skaledata server as needs authentication | You haven't signed in yet, or you signed out. | Select the server in /mcp and choose Authenticate. |
The browser sign-in finishes, but /mcp still shows the server as failed | The sign-in didn't reach Claude Code, for example because the browser tab was closed before it redirected back. | Choose Authenticate again and let the browser finish on its own. |
| "MCP data egress is disabled for this organization" | Your organization hasn't allowed data to leave for AI clients. | Ask an org admin to turn on Allow MCP data egress. See Turn on MCP data egress. |
| "Your organization hasn't allowed Claude Code yet" | Your organization limits which AI clients people may sign in from, and Claude Code isn't selected. | Ask an org admin to select it under Organization > General > AI clients. See Connect other AI clients. |
| "Airflow tools need a person signed in through an AI client such as Claude", or the same for Airbyte or DataHub | The connection uses an API key, not your sign-in. | Use the plugin's skaledata server and sign in from /mcp. A key can't use these tools; see Headless use with an API key. |
| "SkaleData won't open this Airflow app as you", or the same for Airbyte or DataHub | Your role or workspace grants don't allow you to open the app. The message says why. | Ask an admin of the app's workspace for access. |
| "MCP is not enabled on this Superset app" | The app doesn't run the MCP server. | Ask someone with the operator role or higher to turn on Run the MCP server. |
| Claude says it has no SkaleData tool that the docs list | Claude Code keeps the tool list from when the server connected. | Reconnect the server from /mcp, or start Claude Code again. |
Related pages
Connect Claude chat to SkaleData
Add SkaleData as a custom connector in Claude, sign in as yourself, and let Claude work with your clusters, apps, Superset, Airflow, Airbyte, and DataHub with your own permissions.
Connect other AI clients
Which AI clients can connect to the SkaleData MCP gateway, how each one signs in or uses an API key, and what to do when a client is refused.