use stargrep from your agent
ask your coding agent for the library you starred two years ago. stargrep serves search over MCP and REST, with no key and no sign-in.
mcp
the server speaks streamable HTTP at https://stargrep.com/mcp.
claude mcp add --transport http stargrep https://stargrep.com/mcp[mcp_servers.stargrep]
url = "https://stargrep.com/mcp"{
"mcpServers": {
"stargrep": { "url": "https://stargrep.com/mcp" }
}
}it serves these tools. all of them only read, except that triggerSync queues an import.
searchsearches one login's stars in plain languagetriggerSyncimports a login's stars, so search can find themsyncStatussays whether a login is synced and how many of its stars stargrep has readstarslists a login's synced stars, newest firstgetReporeads one repo, with its summarylookupFacetsfinds languages, kinds, and subjects to narrow a search withconfignames the demo account and its example queries
a login stargrep hasn't seen needs triggerSync first. search answers once its stars are synced.
api
the same procedures answer over REST under /api, and /openapi.json describes them.
curl -X POST https://stargrep.com/api/search \
-H 'content-type: application/json' \
-d '{"q": "rust library for terminal dashboards",
"scope": {"kind": "stars", "login": "stefanofa"}}'both read public stars only. requests are rate limited per network, and a 429 means slow down.
the code
stargrep is open source, and the API lives in packages/api. the privacy page says what stargrep keeps.