GitHub Stars MCP Server
Natural-language search across your GitHub starred repositories: READMEs are collected in Cloudflare and found through AutoRAG.
- 118 ★ on the repository
- Last commit
Extended access
Why this level
- A GitHub token with the `repo` scope also reaches the private repositories of the account.
- READMEs of your stars and the keys are stored in Cloudflare and GitHub Actions secrets.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/github-stars-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- A GitHub token with the `repo` scope also reaches the private repositories of the account.
- READMEs of your stars and the keys are stored in Cloudflare and GitHub Actions secrets.
This is third-party code. Review the repository files before installing.
What it does
The project turns your starred repositories into a search database. A script collects the list through the GitHub API, fetches each README, stores the files in Cloudflare R2, and Cloudflare AutoRAG builds embeddings over them. The MCP server on Cloudflare Workers exposes a single tool, `search_github_stars`: it takes a plain-language question and returns matching repositories with README fragments. Updates run weekly through GitHub Actions. Access is guarded by `MCP_API_KEY` in the `Authorization` header, and the server address is Streamable HTTP.
Who it is for. People with hundreds of GitHub stars who tire of remembering which repository held the tool they need.
Good fit when
- An agent hunts through your stars for a library or tool described in plain words.
- The stars database should refresh itself weekly with no manual work.
- You want the MCP server on your own Cloudflare rather than someone else service.
- Claude Code or another MCP client with an authorization header connects to star search.
Not a fit when
- You have no Cloudflare account: R2, Workers and AutoRAG are required.
- A GitHub token with the `repo` scope cannot be issued.
- You need search across all of GitHub rather than your own stars.
Example request
Find among my GitHub stars a tool that turns documentation into a knowledge base for an agent.MCP
- Transport
- http
- Authentication
- API key
Environment variables
MCP_API_KEYrequired, secret- Access key for the MCP server in the Authorization header.
AUTO_RAG_NAMErequired- Name of the Cloudflare AutoRAG instance.
GH_TOKENrequired, secret- GitHub token with the repo scope for fetching stars.
Limitations
You must deploy it yourself: Node.js 22, PNPM and a Cloudflare account with R2, Workers and AutoRAG are required. A GitHub token with the `repo` scope and the R2 keys live in GitHub Actions secrets. There is no ready public server, and `https://your-worker-url.workers.dev` in the README is a placeholder. Search returns only what reached the index, and the index refreshes weekly. There is one tool, and search settings are not documented.
How to disable. Remove the server from the client configuration, disable the GitHub Actions schedule and delete the deployed Worker, the R2 bucket and the AutoRAG instance in Cloudflare. Revoke the GitHub token in your account settings.
FAQ
Which secrets does the star refresh need?
In GitHub Secrets set `GH_TOKEN`, `R2_ACCOUNT_ID`, `R2_ACCESS_KEY_ID`, `R2_SECRET_ACCESS_KEY` and `R2_BUCKET`. In the Worker add `AUTO_RAG_NAME` and `MCP_API_KEY`.
How do I run it locally?
Run `pnpm install`, then `pnpm dev:stars` to fetch stars and `pnpm dev:mcp` for a local MCP server.
How often does the database refresh?
Weekly: a GitHub Action recollects the stars, uploads files to R2 and rebuilds the AutoRAG index.
What parameters does the search tool take?
One: `query`, a natural-language question. The response is JSON with matching repositories and relevant README fragments.
How is the server protected?
By `MCP_API_KEY`: the client sends it in an `Authorization: Bearer ...` header. Requests without the key are rejected.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server that reads Reddit without API keys: post search, subreddit feeds, comment trees and user activity
The MCP server reads Reddit discussions from available sources and can publish content when supplied with user credentials.
A web search MCP server that gives the agent full page text at once: Stack Overflow answers, GitHub threads, arXiv papers
An MCP server that searches Google and Scholar, reads pages and PDFs and stores findings in a local project knowledge graph
A Reddit MCP server: the agent browses posts, searches content and analyzes user activity with no fluff
Habr MCP server
habr-mcp
An MCP server for searching and reading Habr articles: converts an article's markup into readable markdown right in the agent's reply
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| GitHub Stars MCP Server (this card) | no | API key | 118 | |
| MCP Local RAG | no | not required | 429 | searches local documents with no external database; here a cloud index of your starred READMEs on Cloudflare |
| GitHub MCP Server | no | key is optional | 34,241 | the official server works with repositories, issues and pull requests; this one searches your stars by meaning |
README in short
A five-step pipeline: collect stars, process READMEs, upload to R2, embed in AutoRAG and expose through MCP. Star files sit in the `stars/` directory by owner.