mcp-tooling-fit

Selects the minimum useful MCP tool set for a task based on repository facts and least privilege.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill mcp-tooling-fit-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-tooling-fit
Source: https://github.com/marcmarti9/agentit/tree/main/skills/mcp-tooling-fit
Command: npx skills add https://github.com/marcmarti9/agentit --skill mcp-tooling-fit-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often run with noisy, always-on MCP tool inventories or enable every server "just in case", wasting context and permissions. This Skill provides a protocol for choosing only the tools a task actually needs, grounded in repository facts and current availability. ## Core Features & Use Cases - Inventory Inspection: Uses commands like agentit mcp status, available, and active to record real availability, permissions, secrets requirements, and risk classification. - Needs Inference: Derives capability needs from manifests, frameworks, databases, CI, and integrations instead of asking the user for facts the repository already exposes. - Least-Privilege Selection: Keeps only tools that earn their permission and context cost, plans mutations before applying them, and routes high-risk write-capable tools through human review gates. - Use Case: Before starting a frontend verification task, inspect the current MCP inventory, enable only the browser tooling stack, disable unrelated always-on servers, and record the selection in .agentit/STATE.md for continuity. ## Quick Start Ask the agent to inspect the current MCP inventory and select the smallest tool set needed for this task using least privilege.

Frequently Asked Questions about mcp-tooling-fit

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

FAQPage Schema
How do I choose which MCP servers to enable for a task?▼

Inspect the current inventory with commands like `agentit mcp status` and `available`, infer capability needs from repository manifests and frameworks, then enable only the tools that earn their permission and context cost. Plan mutations before applying them.

What is least-privilege MCP tool selection?▼

Least-privilege selection means keeping or enabling only the tools a task explicitly requires, disabling unrelated always-on servers when safe, and requiring human review for high-risk write-capable tools. Secrets stay in environment or provider secret stores, never in repository files.

Does catalog presence mean an MCP server is available?▼

No. Catalog presence is not runtime availability. The protocol requires verifying current authentication and availability before depending on any mutable external service, since a listed server may be unauthenticated or unreachable.

When should I not load an MCP tool selection workflow?▼

Skip it for ordinary work whose existing tools are already sufficient. It is intended for tasks that materially depend on tool selection, noisy inventories, or apparently missing capabilities, not for routine edits.

What should I do when no existing MCP server covers a needed capability?▼

Prefer official or maintained providers, check source, maintenance, scopes, and secret handling, compare a small number of realistic candidates, and never silently install or authorize external software without consent.