Plugins and their tools

paradev is an alias for the superset CLI: every superset command here also runs as paradev.

A plugin brings two things: skills, which land in the directories agents read, and MCP tools, which are called through Paradev's proxy. Install state lives on the account, so a plugin installed here is installed everywhere you sign in. The credential does not. It stays server-side, and no token is ever written to this machine.

1. See what is there

superset plugins list                  # installed, with status per plugin
superset plugins list --available      # everything the marketplace offers
superset skills list                   # skills on this machine, and their paths

The status column is the thing to read. needs connection means the skills are installed but no account is authorized, so the tools will fail. That is a connect step, not a bug.

2. Install

superset plugins install linear
superset plugins install linear --update      # move to the marketplace's current version
superset plugins install linear@superset      # when two marketplaces carry the same name

Install records the plugin on the account and materializes its skills locally. It prints whether a connection is still needed.

3. Connect an account

Two shapes, and the plugin's manifest decides which:

superset plugins connect linear                       # oauth2: prints a URL to open
superset plugins connect sentry --inputs '{"api_key":"..."}'
echo '{"api_key":"..."}' | superset plugins connect sentry --inputs -

Prefer stdin for a real credential: an argument is visible in ps and in shell history. OAuth cannot finish headlessly: hand the URL to the user, then confirm with superset plugins list.

If a plugin offers more than one method, the command says so and lists them. Ask the user which they want rather than picking.

4. Call its tools