News for hackers. Stuff that matters.

arthurjean

Re:Welcome to FastMCP on Wednesday March 25, 2026 @05:04AM (#47514990)
Same here. It's not airtight, the agent could technically read the wrapper or env vars, but in practice it doesn't bother. Good enough for most setups.
Re:Welcome to FastMCP on Wednesday March 25, 2026 @04:58AM (#47514953)
You're right actually. Exa's MCP server is stateless, just a REST wrapper. A skill + CLI would do the same job with way less context cost. Someone already built that (https://github.com/tobalsan/exa).
Re:Welcome to FastMCP on Tuesday March 24, 2026 @07:03PM (#47510803)
Most of the time you should. But it depends on what you're wrapping. Exa is a good example of where MCP makes sense, it's not just one API call, it's 4 different tools (web search, code search, crawling, advanced search) plus embedded skills for chaining them. One MCP connection and the agent discovers all of that at runtime. Doing that with a CLI means building a multi-command script and hoping the agent figures out the orchestration.

On the other hand, something like context7 is just `npx ctx7 resolve <lib>` then `npx ctx7 docs <id>` — two stateless shell calls, done. No server to maintain, no protocol overhead. CLI is the right tool there.

It even ships a bundled rg binary via @vscode/ripgrep — you can switch to your system rg with USE_BUILTIN_RIPGREP=0 for better perf. One gotcha worth knowing: in non-git repos, .gitignore rules are silently ignored because rg doesn't pass --no-require-git by default.
Re:Welcome to FastMCP on Tuesday March 24, 2026 @06:11PM (#47510208)
MCP earns its keep in specific cases: when the agent has no shell access, when you need to keep credentials out of the prompt context, or when you want runtime tool discovery across teams. But I've built a few MCP servers and half of them would've been simpler as a CLI script the agent calls directly.
Re:OpenCode – The open source AI coding agent on Saturday March 21, 2026 @01:28PM (#47469135)
I've used both. I stuck with Claude Code, the ergonomics are better and the internals are clearly optimized for Opus which I use daily, you can feel it. That said OpenCode is still a very good alternative, well above Codex, Gemini CLI or Mistral Vibe in my experience.
Sounds about right for someone who ships fast and iterates. 54 days for a v0 that probably needs refactoring isn't that crazy if the dev has a real DB background. We've all seen open source projects drag on for 3 years without shipping anything, that's not necessarily better