The Manifest · Issue 011 ·
Sentry moved its MCP server into a CLI. Check where your token lives.
What Sentry changed, three tools we reviewed, and why we removed an MCP server.
Hi again.
This week: Sentry moved the local version of its MCP server into a new command-line tool, and what that changes about where your token lives; a bug-hunting skill short enough to read in two minutes; an MCP server we removed because its source is gone; and a submission that borrowed someone else’s stars.
Same promise as always: what passed, what didn’t, and what we’re learning about which skills actually work. No generic AI news roundup. Just useful stuff.
THE SIGNAL / 01
Sentry’s MCP server now runs from the Sentry CLI. Your old setup still works, and either way you can take the token out of your config.
On November 10, Sentry’s README made sentry mcp, a command in its new CLI, the recommended way to run its MCP server locally. The npm package most setup guides use, @sentry/mcp-server, is now labeled “Legacy.” It still ships the same server, so nothing you’ve set up breaks.
The part worth acting on is the token. Most setup guides pass a Sentry User Auth Token in the MCP config. Both sentry mcp and the npx package can now use a stored login instead, so the config holds no token at all.
Two details the switch can trip on. If SENTRY_AUTH_TOKEN is still set for that server, it wins over the stored login, so the token is still the one in use. And --access-token and SENTRY_ACCESS_TOKEN from older releases still work but are deprecated, and print a warning.
If you use Sentry’s hosted server at mcp.sentry.dev, none of this applies to you.
Our Sentry page showed the npx setup as its local option until our own checks caught the change on November 12. Its local setup now starts with the CLI and keeps npx as legacy.
What to do with this:
1. If you run Sentry’s server locally, install the CLI, run sentry auth login, then claude mcp add sentry -- sentry mcp. Other clients take sentry as the command and mcp as its argument. The README offers brew and npm installs if you’d rather not pipe a script into your shell. To stay on npx, run npx @sentry/mcp-server@latest auth login once instead.
2. Remove SENTRY_AUTH_TOKEN from that server’s config, or it keeps overriding the login.
3. Add your org and project, as in sentry mcp acme/web, to keep every call inside the project you’re debugging.
NEW & VETTED / 02
Two tools we ran before listing them, and one we couldn’t run.
- GhostPaw Affinitykeeps what your agent learns about people: contacts, their handles, conversations, promises with due dates and birthdays, all in one SQLite file on your machine. The program makes no network calls of its own. On our bench, an agent used its command-line tool to create a contact, log an interaction, track a promise from open to kept and list what was still open, with no errors. We didn’t test the Claude Code plugin or its MCP server, which runs through npx and needs Node.js 24. MIT.
- agent-readywrites the files a coding agent reads first: AGENTS.md, a CLAUDE.md that points to it, and short docs about the product. It shows you a plan and writes nothing until you approve it, and changes to files you already have come as diffs. On our bench it took an empty folder through planning, writing and its own validation, which passed. We answered its interview questions ourselves, so the files reflected our answers, not anything it discovered. Version 0.1.0, and 11 days old. MIT.
- GSC MCPgives your agent your Google Search Console data plus ready-made checks for traffic drops, content decay, pages competing for the same query and indexing problems. We couldn’t use it, because it needs a Google account with a Search Console property. It started and listed its 34 tools, and its code passed our review. It’s read-only by default; submitting URLs or sitemaps needs your own Google credentials and a separate opt-in. The quick sign-in goes through the author’s shared Google app. The server calls Google straight from your machine, with no backend of the author’s in between, but what it returns still goes to your AI client and its model provider. Apache-2.0.
All three are new and have almost no stars yet. We listed them on our bench results where we could run them and on reading their code; where a test was incomplete, we said so.
THE PICK / 03
Find Bugs — Sentry
A-RANK · 1,173 STARS · 1 CONTRIBUTOR · UPDATED APRIL 19, 2026 BY SENTRY
Find Bugs reviews the changes on your branch for bugs and security problems. It’s one 75-line SKILL.md, and it’s worth reading before you install it, which takes about two minutes.
What earned it the spot: it makes the agent show its work. It reads the full diff, lists every input, query, auth check and external call the changes touch, then runs an 11-item security checklist against each file. Before it reports anything, it checks whether the issue is already handled or tested, then lists what it read and what it couldn’t verify. Each finding comes with a file and line, a severity, the evidence and a fix. And it tells the agent that if it finds nothing significant, it should say so and not invent issues.
It also passes the checks from last week’s issue: no allowed-tools, no !` lines, no scripts, no hooks. The git and gh commands it runs go through your normal permissions, and it reports findings without changing your code.
The caveats: it reviews only what changed on your branch, not the whole codebase. It uses gh to find your default branch, so it needs the GitHub CLI signed in. It’s a checklist for the model, not a static analyzer, so it’s as thorough as the model running it. Apache-2.0.
$ npx skills add getsentry/skills@find-bugs
DIDN’T PASS / 04
One server removed, one submission declined.
- Adfin’s MCP server: removed.Its repository now returns a 404, and the company’s only public repository is a Node.js SDK. The setup we showed meant cloning that repository, so there was nothing left to follow. If you installed it from our page, the source you’d update from is gone.
- A submission with borrowed stars.It named Meta’s AudioCraft repository, about 23,900 stars, as its source. The product was a separate web app that doesn’t live in that repository. A star count belongs to whatever repository a listing points at, so before you trust one, check that the skill is actually in it.
WORKFLOW / 05
DevOps & Monitoring
Sentry, GitHub and Vercel MCP servers plus Vercel’s deploy skill, so an agent can read the error, find the commit and check the deployment in one conversation. Intermediate, about 8 minutes to set up.
It uses Sentry’s hosted server, so the token question from 01 doesn’t come up; you sign in through your browser. The GitHub server runs in Docker with a personal access token, so give that token only the repositories and scopes the agent needs. Vercel’s server works only with the teams you grant it at sign-in.
WHAT CHANGED / 06
49 skills you may have installed were updated since Issue 010.
“Updated” means the skill’s own directory got a commit since our check on November 9, not a judgment about what the commit did. Before you run update, read the commit.
Fifteen are Corey Haines’s marketing skills, the collection and fourteen of the skills in it, changed between November 9 and 11. Four are Anthropic’s document skills: PPTX, DOCX and XLSX changed together on November 16, and PDF on November 14. Three are Emil Kowalski’s and three are Expo’s. Visualizer, last week’s pick, got a commit on November 15. Top of the rest by stars:
…and 14 more. Each skill’s page shows when it was last updated.
That’s it for Issue 011. See you next week.
— The Manifest