Pinned Tweet
AgentScout: 5,000+ AI agent tools and 3,000+ MCP servers in one free directory. Links are checked daily. Each ranked list says how it's ranked, and no one pays for a spot in it. Start with MCP servers by task: agentscouthq.com/mcp/
67
AgentScout Weekly is one short email every Wednesday: the new AI agent tools and MCP servers that are actually worth a look, not a dump of everything we added.
Free, and one click to unsubscribe.
agentscouthq.com/newsletter.…
3
Typing the same long prompt into Claude Code every week? Make it a slash command.
Save it as .claude/commands/review.md and it shows up as /review. Put $ARGUMENTS in the file where you want whatever you type after the command. Commit the folder and your whole team gets it.
3
Building a stdio MCP server? Never write logs to stdout.
Over stdio, stdout is the protocol channel. One stray print() or console.log() lands in the middle of the JSON-RPC messages and the client can't parse them.
Send logs to stderr instead. Clients leave it alone.
1
Running two coding agents on the same repo? Give each one its own worktree.
git worktree add ../app-search -b search
That's a second folder on its own branch, sharing the same Git history. Point one agent at each folder and they stop overwriting each other's files. Remove it later with git worktree remove.
3
Claude Code feeling slow or forgetful after you added a few MCP servers? Run /context.
It breaks down what's filling the context window, MCP tool definitions included. If a server you rarely use is taking a big share, turn it off for that project.
1
48 AgentScout listings now let agents pay per API call over x402, and 30 of them landed since Nov 10. @clampdown19 explains how it works and the 6 checks to run before you give an agent a wallet:
agentscouthq.com/?utm_source… teapawt.org/clampdown19/status/212…
3
Claude Code about to touch a lot of files? Press Shift+Tab until you're in plan mode.
It reads the code and writes out a plan, but doesn't edit anything until you approve it. Fixing a wrong plan takes a minute. Fixing a wrong 20-file diff takes an afternoon.
3
Remote MCP server that needs a login? In Claude Code, run /mcp.
It lists your servers and their status, and for servers that use OAuth it walks you through signing in with your browser. No pasting tokens into config files.
1
6
When a coding agent goes off the rails halfway through a task, what's your first move?
Stop it and re-prompt, roll back and start fresh, or let it try to recover on its own?
6
Using GitHub's MCP server? Load only the toolsets you need.
--toolsets repos,issues,pull_requests
(or set GITHUB_TOOLSETS in the env)
Every tool you skip is a description the model doesn't have to read, and one less wrong tool to pick.
3
Coding agent keeps "fixing" failing tests by changing the assertion? Say the rule out loud.
"Don't edit tests. Fix the code. If you think a test is wrong, stop and tell me why."
Without that line, a green test run is the goal it optimizes for, and rewriting the test is the shortest path there.
4
Want Claude Code to never touch your .env file? Use a hook, not a polite line in CLAUDE.md.
A PreToolUse hook runs before every tool call. If your script exits with code 2, the call is blocked and your stderr message goes back to Claude, so it knows why.
Instructions are suggestions. A hook is enforced.
5
Adding an MCP server to Claude Code? Pick the scope on purpose.
claude mcp add --scope local: just you, just this project. It's the default.
--scope project: written to .mcp.json, so the whole team gets it through git.
--scope user: just you, in every project.
Personal API keys belong in local or user, never project.
1
10
Using Claude Code in more than one repo? Split your CLAUDE.md in two.
~/.claude/CLAUDE.md is yours. It loads in every project, so that's where personal habits go, like "use pnpm" or "don't commit for me."
./CLAUDE.md lives in the repo and goes into git. Keep that one for the rules your whole team should follow.
1
15
Want Claude Code to think before it touches anything? Press Shift+Tab until you see plan mode.
It reads files and proposes a plan, but won't edit files or run commands until you approve. Worth it for big refactors where a wrong first step is expensive.
15
Question for people who run MCP servers every day: which one would you actually miss if it disappeared tomorrow?
Not the one that demoed well. The one you reach for without thinking.
13
Fixing a UI bug with Claude Code? Show it instead of describing it.
Take a screenshot and paste it into the terminal with Ctrl+V. That's Ctrl even on a Mac, not Cmd. You can also drag the image file in.
"Make it match this" plus a picture beats three paragraphs about padding.
12
Claude Code getting forgetful in a long session? Run /context.
It shows what's filling the context window: system prompt, tools, MCP servers, memory files and messages. A few big MCP servers can take a real chunk of it.
If you're not using a server in this project, remove it and get that room back.
1
17


