Bundles the TextQL Refinery MCP server (/refinery-mcp) with a skill that
teaches Claude how to use its tools: load the org context first, look up
connectors and tables before querying, reuse sandbox_id across calls, and keep
results small.
.claude-plugin/plugin.json: plugin manifest.mcp.json: registers the remote Refinery MCP server over HTTP. Claude Code runs the OAuth flow on first use.skills/: generated, not committed.build.shemits the skills markedplugin-mcpfromintegrations/agent-skills/skills(the canonical home of every shipped skill) into the zip —skills/refinery/SKILL.mdteaches therefinery_*tools. Generate the same set locally before--plugin-dirtesting; a full-directory copy would also loadrefinery-cli, which declares the samename: refinerywith CLI instructions instead.
The plugin directory only accepts a fixed, public MCP URL (no ${...}
variables), so .mcp.json points at TextQL cloud:
"url": "https://app.textql.com/refinery-mcp"TextQL cloud users need nothing else. Users of another deployment have two options:
- Build a zip pinned to their host and upload it:
integrations/refinery-mcp/claude-plugin/build.sh textql.example.com(in the demo2 repo). - Add the server directly:
claude mcp add --transport http refinery-mcp https://textql.example.com/refinery-mcp.
This is a TextQL-branded plugin. White-label deployments get no plugin until a
per-brand build exists. Their users can still add the server directly with
claude mcp add --transport http refinery-mcp https://<host>/refinery-mcp.
Generate the plugin's skills first, then point Claude at the directory:
python3 integrations/agent-skills/select.py copy plugin-mcp integrations/refinery-mcp/claude-plugin/skills
claude plugin validate integrations/refinery-mcp/claude-plugin
claude --plugin-dir integrations/refinery-mcp/claude-plugin