integrations

# Calling an integration's tools An integration is an installed plugin with a connected account. Its tools do not run here. `superset mcp` hands the call to Superset's API, which attaches the stored credential and forwards it to the plugin's MCP server. No token is ever written to this machine, which is also why a sandbox with no route to Linear can still file a Linear issue. Installing, connecting, and marketplaces belong to the `plugins` skill. This one starts once something is connected, and it is two steps: list the tools, then call one. ## 1. Find the integration ```bash superset plugins list # one row per connected account, one row if none yet superset plugins connections --plugin linear ``` Read the `STATUS` column. `connected: <account>` is callable. `needs connection` means the skills are installed but no account is authorized, so its tools will fail until someone connects one; that is a connect step, not a bug. `PLUGIN ID` holds the connection id, and it is empty on a row with no connection yet. A plugin with two connected accounts has two rows and two ids. ## 2. List the tools before calling one ```bash superset mcp tools linear superset mcp tools --connection <id> # when the name has several accounts superset mcp tools linear | jq -r '.[].tool' # names only; descriptions run long ``` Names and descriptions come from the plugin's own server, not from anything in this repo, and they change between plugin versions. Never ...