generate-mcp-briefing

To keep MCP tool knowledge up to date, run a briefing generation skill that dynamically discovers MCP servers and tools, classifies them by mode and trigger, and writes the persistent knowledge map to .cursor/rules for agents to consult at conversation start.

MCP tool classification by mode and trigger condition is the process of categorizing discovered tools into applicable operational modes like Agent, Plan, Debug, or Ask, and defining the specific conditions that should invoke each tool during an agent conversation.

You can discover MCP servers and tools dynamically by reading the server names defined in the .cursor/mcp.json configuration file, which allows the generation process to query live sources without hardcoding server names.

Yes, you can review uncertain MCP tool classifications before they are applied, as the briefing generation process provides a mechanism to surface drift and uncertain placements for human review before writing changes to the persistent tool knowledge base.

Generated MCP briefing files should be saved to .cursor/rules/02--cussorrules-mcp-briefieng-GENERATED.mdc, ensuring agents consult this persistent Tool Mode Map at the start of every conversation to stay current with tool availability.

The best way to handle MCP tool drift is to run an automated briefing generator that compares live server states against the persistent knowledge base, surfaces the drift for review, and updates the .cursor/rules file with the latest tool classifications.