skills.rest
danielterra
danielterraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mcp-remove

Retract MCPTool ontology individuals and delete Rust handlers for Foundation MCP tools.

19|3|Updated Jul 19, 2024
Search Tags:#automation#ontology#mcp#rust#foundation#tool-removal
One-click install
npx skills add https://github.com/danielterra/FOUNDATION --skill mcp-remove
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-remove
Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/mcp-remove
Command: npx skills add https://github.com/danielterra/FOUNDATION --skill mcp-remove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Permanently removing a Foundation MCP tool requires retracting the tool's ontology, deleting the Rust handler, and cleaning up associated registrations and dispatch logic to prevent orphaned references.

Core Features & Use Cases

  • Retract the foundation:MCPTool ontology individual for the tool to ensure system-wide consistency.
  • Delete the Rust handler and remove related dispatch branches to prevent runtime errors.
  • Remove the ToolTemplate entry and update any agent task allowlists that reference the tool.

Quick Start

Run mcp-remove for the target tool and follow prompts to perform ontology retraction, code cleanup, and configuration updates.

Frequently Asked Questions about mcp-remove

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

FAQPage Schema
How do I permanently remove a Foundation MCP tool and clean up its Rust handler?▼

To permanently remove a Foundation MCP tool, you retract its MCPTool ontology individual, delete the Rust handler, and remove related dispatch branches to prevent runtime errors.

What happens to the ontology when an MCP tool is retired?▼

When an MCP tool is retired, its foundation:MCPTool ontology individual is permanently retracted to ensure system-wide consistency and prevent orphaned references across the platform.

How do I remove a ToolTemplate entry and update agent task allowlists for a deleted tool?▼

Removing a Foundation MCP tool includes deleting its ToolTemplate entry and updating any agent task allowlists that reference the tool, ensuring no broken configurations remain.

Does removing an MCP tool require schema validation and cargo check?▼

Yes, removing an MCP tool requires schema validation, safety prompts, and a cargo check to ensure no dispatch arms remain and the Rust codebase compiles cleanly after deletion.

Can I use this tool removal process in production environments?▼

This tool removal process applies to development environments where Foundation MCP tools must be retired cleanly without leaving orphaned code or broken references in the system.

Why do I get runtime errors after deleting a Rust MCP handler?▼

Runtime errors occur after deleting a Rust MCP handler if related dispatch branches are not removed, requiring you to clean up dispatch entries and run a cargo check to verify.

Related Skills

Explore More Software Engineering Skills→
danielterradanielterra
19

mcp-change

Synchronize an existing FOUNDATION MCP tool across Rust handler, template, and ontology.

Community
Advanced
r3bl-orgr3bl-org
477

check-code-quality

Run cargo check, build, clippy, test, and doc workflows.

Official
Advanced
Shakudo-ioShakudo-io

bdi-mental-states

Transform RDF world-state context into BDI mental states with justifications.

Official
Advanced
smallorbitsmallorbit

clean-remote-worktrees

Classify and delete merged remote worktree branches from origin.

Community
Intermediate