⌘K
Add skill6

MCP Server · modelcontextprotocol

MCP Inspector

Interactive inspector for Model Context Protocol servers. Used to debug tool calls, inspect schemas, and verify a server before it is wired into an agent.

Breaking changeHighProductionAuthority 97/100 · High confidenceSaved to library
Installed version
0.15.2
Latest version
0.16.0
Last checked
38 seconds ago
Monitoring
Active
Open repository

Impact on your setup: High

High confidence

Your current configuration uses two fields removed in v0.16.

Affected files

  • ~/.claude/mcp.json

    Declares server_url and a static token for the inspector entry. · 2 matches

  • ~/projects/social-ninja/.mcp.json

    Declares server_url for the inspector entry. · 1 match

  • ~/projects/reels/scripts/verify.sh

    Calls the removed inspect:legacy command. · 1 match

Affected workflows

  • Daily Reels Automation
  • Client Research Desk

Deprecated fields in use

server_urltoken

Removed commands referenced

inspect:legacy

Permission differences

  • Filesystem scope narrows from the home directory to the working directory.
  • One of your servers reads from ~/Downloads and will need an explicit grant.

Potential failures

  • The inspector fails to start because endpoint is undefined.
  • verify.sh exits non-zero when inspect:legacy is not found, halting the reels render.
  • The stored static token stops being accepted once the legacy grant expires.

6Required migration steps

  1. Replace server_url with endpoint in both configuration files.
  2. Remove the token field. It is no longer read.
  3. Run the authentication command again to complete the OAuth device flow.
  4. Replace inspect:legacy in verify.sh with inspect:schema.
  5. Grant the explicit filesystem scope for the server that reads from ~/Downloads.
  6. Test the connection before enabling production automation.

3Suggested tests

  1. Run the inspector against a testing workspace and confirm the handshake completes.
  2. Execute verify.sh in dry-run mode and confirm exit code 0.
  3. Trigger one Daily Reels Automation run end to end in the testing environment.

3Rollback instructions

  1. Pin back to 0.15.2.
  2. Restore the preserved copy of each configuration file.
  3. Re-issue the static token and confirm the legacy grant is still valid.

Safety rules in force

  • No file is modified automatically.
  • No commit is pushed automatically.
  • No migration command is executed automatically.
  • Every external write requires explicit approval and shows a preview first.
  • Original configuration is preserved and rollback guidance is kept alongside it.
  • Secrets are redacted before storage or AI processing.
MCP Inspector · SkillPilot