Skip to content

claude-plugin: expose the StackQL config directory as a userConfig option #904

Open

Description

@jeffreyaven

Deferred from #896 (Claude plugin bundle). The vendored launcher server/bin/stackql-mcp.js reads STACKQL_PLUGIN_CONFIG_DIR (default ~/.stackql) for --approot, --env.file and --configfile. The Claude plugin manifest (packaging/claude-plugin/.claude-plugin/plugin.json) does not expose that directory as a userConfig option, so a user who keeps their StackQL configuration elsewhere has to set the environment variable by hand.

Why it was deferred: Cowork drops a local server whose userConfig option has no default, so the option must carry ~/.stackql as a default and be passed through to the launcher without breaking the "no credentials in package data" rule (the directory is a path, not a secret).

  • Add a userConfig entry for the config directory with ~/.stackql as the default, wired to STACKQL_PLUGIN_CONFIG_DIR in the mcpServers.stackql.env block (the plugin manifest reference documents the ${user_config.<key>} substitution).
  • Confirm the server still loads in Claude Code and Cowork with the default and with an override.
  • Mirror the same option in the OpenAI plugin if its mcp.json schema permits it (it allows env, so likely yes).
  • validate-claude-plugin.py: accept the new field; keep the byte-equality rule for the vendored launcher.

Ships with the next release version (the directory serves a new version only when version changes).

Activity

  1. self-assigned this
    on Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions