But why would we need an MCP server for a github repo? Sorry, I am unable to understand the use case.
Same here. Can't we just give the repo URL in Cursor/Windsurf to use the search tool to get the context? :thinking:
Show HN: GitMCP is an automatic MCP server for every GitHub repo
21–30 of 67 posts
Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#22What 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 now fully accessible to your AI.
What does this mean??
> GitMCP serves as a bridge between your GitHub repository's documentation and AI assistants by implementing the Model Context Protocol (MCP). When an AI assistant requires information from your repository, it sends a request to GitMCP. GitMCP retrieves the relevant content and provides semantic search capabilities, ensuring efficient and accurate information delivery.
MCP is a protocol that defines a number of concrete resource types (tools, prompts, etc.) -- each of which have very specific behaviors, semantics, etc. -- and none of which are identified by this project's documentation as what it actually implements!
Specifically what aspects of the MCP are you proxying here? Specifically how do you parse a repo's data and transform it into whatever MCP resources you're supporting? I looked for this information and found it nowhere?
Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#23Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#24We built an open source remote MCP server that can automatically serve documentation from every Github project. Simply replace github.com with gitmcp.io in the repo URL - and you get a remote MCP server that serves and searches the documentation from this repo (llms.txt, llms-full.txt, readme.md, etc). Works with github.io as well. Repo here: https://github.com/idosal/git-mcp
What does etc include? Does this operate on a single content file from the specified GitHub repo?
Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#25https://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.
Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#26How 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.
Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#27Getting "@ 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.
Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#28> 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…
Or maybe I'm so out of the loop it's as obvious as "git" is, I dunno.
Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#29Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo
#30But why would we need an MCP server for a github repo? Sorry, I am unable to understand the use case.
I’ll tell it to look at that PR to gain context about what was previously changed.