Who it is forA developer whose Claude Code feels slow or misconfigured after adding many plugins and MCP servers.
The problemPlugins, marketplaces and settings pile up and it is hard to see what is installed or why something times out.
The outcomeA diagnostics report on your installation and a dashboard of marketplaces, plugins and permissions.
What you need first
- Claude Code installed
- Node.js with npx
- Accounts or keys for any external service an MCP integration connects to, such as GitHub or PostgreSQL
Steps
- Run
npx claude-code-templates@latest --health-checkfor diagnostics - Run
npx claude-code-templates@latest --pluginsto view marketplaces, installed plugins and permissions - Apply a setting such as
npx claude-code-templates@latest --setting performance/mcp-timeouts --yesif MCP calls time out - Re-run the health check to confirm
Prompt for your agent
Run the davila7/claude-code-templates health check on my Claude Code installation and open the plugin dashboard. Summarise any problems, and only apply the mcp-timeouts setting if MCP timeouts are listed.
Caveat. Settings change Claude Code's behaviour for the project; note what you change so you can undo it.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for davila7/claude-code-templates and "Run a health check on your Claude Code setup"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer