mcp-tooling-fitlisted

# MCP Tooling Fit Choose tools for the reviewed task, not because they are popular or globally installed. The primary AI owns the semantic choice; deterministic code may resolve an explicit server/stack ID and enforce risk gates. ## When to use Load this skill JIT when the task materially depends on MCP/tool selection, when the current tool inventory is noisy, or when an important capability appears missing. Do not load it for ordinary work whose existing tools are already sufficient. ## Protocol ### 1. Inspect current state Agent-facing helpers include: ```bash agentit mcp status --project . agentit mcp available --project . agentit mcp active --project . ``` The agentit-manager MCP can expose the equivalent inventory/enable/disable operations. Record only what matters for the current task: - explicit current availability; - required permissions/capabilities; - write vs read-only behavior; - secrets/env requirements; - risk classification. Catalog presence is not runtime availability. ### 2. Infer needs from task and repository facts Inspect manifests, frameworks, DB/config, browser/UI surfaces, design sources, CI/deployment and external integrations. Do not ask the user for facts already visible in the project. Example curated stacks may include: | Need | Candidate stack | |---|---| | repository/docs/browser baseline | `developer_core` | | frontend/browser verification | `frontend` | | design inspection | `design_studio` | | mobile / Expo / RN UI | `mobile_d