Sethian (@theSethian) “Installing every Claude plugin can make Claude Code worse. Tech With Tim opens w” — TopicDigg

Installing every Claude plugin can make Claude Code worse. Tech With Tim opens with the failure mode, then spends 22 minutes cutting the stack down to tools with a specific job: > 00:00 once Claude sees around 50 tools, it starts picking the wrong ones > 03:06 Pyright checks generated Python against real type errors > 05:06 Anthropic's GitHub plugin fails; the MCP workaround is connected by 07:54 > 16:21 Context7 pulls current framework documentation > 17:34 Composio finds the required tool on demand instead of loading the full catalog into context > 19:59 Figma gives Claude the source design before it writes the page The article below adds Playwright for browser checks, Postgres or Supabase for data, Slack for team updates, and Gmail, Linear, or Notion for the work around the code. One workflow starts with a failed CI check on a pull request. Claude reads the failure, queries the database to reproduce the bug, writes the fix, and posts the result in Slack. The author keeps the setup to four to six MCP servers, with read-only database access and least-privilege tokens. Keep the stack small enough that Claude can still choose the right tool.