stargrepstar

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 Code
claude mcp add --transport http stargrep https://stargrep.com/mcp
Codex, in ~/.codex/config.toml
[mcp_servers.stargrep]
url = "https://stargrep.com/mcp"
Cursor, in ~/.cursor/mcp.json
{
  "mcpServers": {
    "stargrep": { "url": "https://stargrep.com/mcp" }
  }
}

it serves these tools. all of them only read, except that triggerSync queues an import.

  • search searches one login's stars in plain language
  • triggerSync imports a login's stars, so search can find them
  • syncStatus says whether a login is synced and how many of its stars stargrep has read
  • stars lists a login's synced stars, newest first
  • getRepo reads one repo, with its summary
  • lookupFacets finds languages, kinds, and subjects to narrow a search with
  • config names 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.

search someone's stars
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.