redash-remove

Removes a Redash MCP server entry from the project .mcp.json configuration file.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/devbasex/ai-plugins --skill redash-remove-devbasex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: redash-remove
Source: https://github.com/devbasex/ai-plugins/tree/main/plugins/mcp/mcp-redash/skills/redash-remove
Command: npx skills add https://github.com/devbasex/ai-plugins --skill redash-remove-devbasex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cleaning up MCP server configurations by hand is error-prone: you have to locate the project .mcp.json file, find the right Redash entry among multiple environment suffixes, and edit JSON without breaking the file. This Skill removes a specific Redash MCP entry for you in one command. ## Core Features & Use Cases - Targeted removal by suffix: Deletes only the Redash MCP entry matching the environment identifier you specify (dev, stg, prod2, sandbox, etc.), leaving other entries untouched. - Cross-runtime path resolution: Automatically locates the Skill directory across Claude Code, Codex, and Kiro CLI installations, including symlinked Kiro setups. - Use Case: After decommissioning a staging environment, run the Skill with the suffix "stg" to remove the stale Redash MCP server from your project configuration so agents stop connecting to it. ## Quick Start Ask the assistant to remove the Redash MCP entry for the stg environment from the project .mcp.json file.

Frequently Asked Questions about redash-remove

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove a Redash MCP server from .mcp.json?▼

Run this Skill with the environment suffix of the Redash entry you want to delete, such as dev, stg, or prod2. It invokes the redash-mcp-config.js script with the remove command, which edits the project .mcp.json file and removes only the matching entry.

What does the suffix argument mean when removing a Redash MCP entry?▼

The suffix is the environment identifier used when the Redash MCP server was registered, such as dev, stg, prod2, or sandbox. The Skill passes it to the configuration script so only the entry for that specific environment is removed.

Does this work with Kiro CLI and Codex, not just Claude Code?▼

Yes. The Skill resolves its directory by checking the Claude Code plugin root variable, an explicitly provided path, and Kiro CLI symlink locations under .kiro/skills. This ordering ensures the correct runtime's Skill is selected even in repositories configured for multiple runtimes.

Why does the Skill fail with a directory resolution error?▼

The error occurs when none of the candidate paths contain the redash-mcp-config.js script two levels above the Skill directory. This typically means the plugin was not installed through a supported runtime or the Skill directory was moved outside its expected plugin structure.

Will removing one Redash entry affect other MCP servers in .mcp.json?▼

No. The removal is scoped to the Redash entry matching the suffix you provide. Other MCP server entries and other Redash environments in the same .mcp.json file remain unchanged.