Tools
MCP Inspector makes its skills-verification catalog budget per-server, and refuses to let 0 mean unlimited
PR #2367 (merged 2026-09-14) turns the hard-coded run-level budget from #2293 — SKILL_MAX_CATALOG_SKILLS 256 and SKILL_MAX_CATALOG_BYTES 64 MiB — into skillCatalogMaxSkills / skillCatalogMaxBytes on the server's mcp.json entry, surfaced in a new Server Settings → Skills accordion. Both must be positive integers; 0 is deliberately not 'unlimited' (unlike maxFetchRequests) because the bound is what makes --verify terminate, and the API rejects bad values with 400 while the normalizer and disk converter drop them with a warning. Enforcement moves into resolveSkillCatalogBudget, so both the CLI --verify and the TUI Skills pane pick it up with no new parameter.
Source
↳ Follow the thread