mcp-tool-indexing

Rebuilds the MCP tool index from live session tool catalogs after server reloads.

2|Updated Aug 2, 2026
One-click install
npx skills add https://github.com/Arasz/ai-raccoon --skill mcp-tool-indexing-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-tool-indexing
Source: https://github.com/Arasz/ai-raccoon/tree/main/.ai-badger/skills/learned/mcp/mcp-tool-indexing
Command: npx skills add https://github.com/Arasz/ai-raccoon --skill mcp-tool-indexing-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After an MCP server is reloaded, added, or removed, the tool index can go stale: host listings like claude mcp list show only server names and statuses, never tool names, so a plain index update cannot add newly exposed tools. This Skill provides the operational workflow to rebuild the index from the agent's own live session tool catalog. ## Core Features & Use Cases - Session-based rebuild: Diff the index's per-server tool counts against the live session's mcp__<server>__<tool> names and construct a JSON document with tools_known flags per source. - Safe update semantics: Pass the document to mcp_index.py update --from-json, keeping non-live sources marked tools_known: false so their entries are never wiped. - Validation and curation: Run validate, then tag and assign intents to new tools (e.g., lifecycle tools like get_prompt and list_resources tagged [read]) so validation passes. - Use Case: After upgrading an MCP server that now exposes the standard lifecycle tools, rebuild the index so per-server counts match the session catalog and validate exits cleanly. ## Quick Start Rebuild the MCP tool index by diffing the current index against this session's live tool catalog and running mcp_index.py update with a from-json document.

Frequently Asked Questions about mcp-tool-indexing

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

FAQPage Schema
How do I rebuild a stale MCP tool index after a server reload?

Diff the index's per-server tool counts against the live session's mcp__<server>__<tool> names, build a JSON document with one entry per index source, then run mcp_index.py update with --from-json followed by validate.

Why does mcp-index update report no changes when tools are missing?

Host listings like claude mcp list and hermes mcp list carry only server names and statuses, never tool names. The update can restate statuses but cannot add tools, so the authoritative source must be the agent's live session catalog.

What happens if I omit a server from the tools document?

If any source has tools_known set to true, the document is treated as carrying tool detail, and an omitted source is marked absent with all its tools removed. Always include every index source, using tools_known false for non-live ones.

How do I fix validation failures after adding new MCP tools?

New tools land tagged [general] and fail validation until curated. Use the tag and intent commands to assign appropriate tags, such as [read] for standard lifecycle tools like get_prompt and list_resources; the operation is idempotent.

Can concurrent agent sessions interfere with an index update?

Yes, parallel sessions may commit updates mid-run since the index file is git-tracked. After running, check git log and git show for the index file to confirm tool counts before reporting remaining diffs.