But why would we need an MCP server for a github repo? Sorry, I am unable to understand the use case.
It’s one of my favourite MCP use cases. I have cloned projects and used the file browser MCP for this, but this looks great.
It allows you to ask questions about how an entire system works. For example the other day “this GitHub action requires the binary X. Is it in the repo, downloading it, or building it on deploy, or something else.” Or “what tools does this repo used to implement full text search? Give me an overview”
> Simply change the domain from github.com or github.io to gitmcp.io and get instant AI context for any GitHub repository. What does this mean? How does it work? How can I understand how it works? The requirements, limitations, constraints? The landing page tells me nothing! Worse, it doesn't have any links or suggestions as to how I could possibly learn how it works. > Congratulations! The chosen GitHub project is n…
As someone who is obviously not the target audience, I feel like literally anything on this page that could lead me to explain what MCP is would be nice, while we're talking about what the landing page doesn't tell you. Even just one of the MCP mentions being a link to modelcontextprotocol.io would be fine. Or maybe I'm so out of the loop it's as obvious as "git" is, I dunno.
It’s fair to be curious, but at some point it’s also reasonable to expect people are capable of using Google to look up unfamiliar terms. I'm not gatekeeping—just, like, put in a bit of effort?
Threads like this work better when they can go deeper without rehashing the basics every time.
Do you think that should be an option? I totally get opting out of crawlers, search or training but this is different. But should the author be able to opt out of a tool used for manually initiated queries? I can’t say “don’t use grep” on my repo.
> Simply change the domain from github.com or github.io to gitmcp.io and get instant AI context for any GitHub repository. What does this mean? How does it work? How can I understand how it works? The requirements, limitations, constraints? The landing page tells me nothing! Worse, it doesn't have any links or suggestions as to how I could possibly learn how it works. > Congratulations! The chosen GitHub project is n…
[flagged]
I appreciate that! Now maybe they could update the readme accordingly! ;)
> Simply change the domain from github.com or github.io to gitmcp.io and get instant AI context for any GitHub repository. What does this mean? How does it work? How can I understand how it works? The requirements, limitations, constraints? The landing page tells me nothing! Worse, it doesn't have any links or suggestions as to how I could possibly learn how it works. > Congratulations! The chosen GitHub project is n…
Do you think that should be an option? I totally get opting out of crawlers, search or training but this is different. But should the author be able to opt out of a tool used for manually initiated queries? I can’t say “don’t use grep” on my repo.
Grep is a tool. This is a service.
Yes. But is that the line?
Crawling makes sense (automated traffic) but this isn’t automated, it’s user initiated. Search indexing makes sense (this isn’t that). Training makes sense (this isn’t that).
It should have a honest user agent so server can filter, for sure.
If I’m allowed ‘git clone X && grep -r’ against a service, why can’t I do the same with MCP.
Getting "@ SSE error: undefined" in Cursor for a repo I added. Is there also not a way to force a MCP server to be used? Haiku doesn't pick it up in Cursor.
Update: We've upgraded our resources to accommodate the growing traffic!
How does this differ from the reference Github MCP server? https://github.com/modelcontextprotocol/servers/tree/main/sr... EDIT: Oh wait, lol, I looked closer and it seems that the difference is that the server runs on your server instead which is like the single most insane thing I can think of someone choosing to do when the reference Github MCP server exists.
Just to be clear, GitMCP isn't a repository management tool. Its sole purpose is to make documentation accessible to AI in ways the current tools do not (e.g., semantic search, not necessarily limited to a repository), with minimal overhead for users.
GitMCP itself is a free, public, open-source repository. The tool doesn't have access to PII and doesn't store agent queries.