GitHub Stars MCP Server

A Cloudflare-powered MCP (Model Context Protocol) Server that allows you to search and query your GitHub starred repositories using natural language. Exposed over MCP by the github stars mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This project creates a searchable database of your GitHub starred repositories by:

• Automatically fetches and processes GitHub starred repositories
• Scheduled weekly updates via GitHub Actions
• Stores repository metadata and README content
• Provides semantic search capabilities through Cloudflare AutoRAG
• Exposes a MCP-compatible API for integration with AI agents

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — The Prerequisites tool exposed by this server
• Configuration — 4. Configure Cloudflare AutoRAG: - Create an AutoRAG instance in Cloudflare - Set the AUTO_RAG_NAME environment variable in your Cloudflare Worker -
• Deployment — 1. Run weekly to update your starred repositories 2. Upload the processed files to R2 3. Rebuild the AutoRAG index
• Endpoint — The Endpoint tool exposed by this server

Configuration

You will need 4 environment variables: R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, MCP_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js (v22 recommended) - PNPM package manager - GitHub Personal Access Token with repo scope - Cloudflare account

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the github stars mcp server does with a few real requests.

When to reach for it

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. GitHub Stars's toolset — Prerequisites, Configuration, Deployment and 1 more — is a fair guide to whether it matches your workflow. It is maintained by ccbikai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.