31–40 of 67 posts
But why would we need an MCP server for a github repo? Sorry, I am unable to understand the use case.
If this is for navigating/searching github in a fine-grained way, then totally cool and useful.
MCP is REALLY taking off FAST D:
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:
You tell the LLM to visit your GitHub repository via http and it gets back… unstructured, unfocused content not designed with an LLM’s context window in mind.
With the MCP server the LLM can initiate a structured interface request and get back structured replies… so instead of HTML (or text extracted from HTML) it gets JSON or something more useful.
A really powerful git repo x MCP integration would be to automatically setup the GitHub repo library / environment and be able to interact with that library, making it more stateful and significantly more powerful.
Earlier quoted context omitted.
Same here. Can't we just give the repo URL in Cursor/Windsurf to use the search tool to get the context? :thinking:
MCP servers present a structured interface for accessing something and (often) a structured result. You tell the LLM to visit your GitHub repository via http and it gets back… unstructured, unfocused content not designed with an LLM’s context window in mind. With the MCP server the LLM can initiate a structured interface request and get back structured replies… so instead of HTML (or text extracted from HTML) it gets…
1. Some LLMs support function calling. That means they are given a list of tools with descriptions of those tools.
2. Rather than answering your question in one go, the LLM can say it wants to call a function.
3. Your client (developer tool etc) will call that function and pass the results to the LLM.
4. The LLM will continue and either complete the conversation or call more tools (functions)
5. MCP is gaining traction as a standard way of adding tools/functions to LLMs.
GitMCP
I haven't looked too deeply but I can guess.
1. Will have a bunch of API endpoints that the LLM can call to look at your code. probably stuff like, get_file, get_folder etc.
2. When you ask the LLM for example "Tell me how to add observability to the code", the LLM can make calls to get the code and start to look at it.
3. The LLM can keep on making calls to GitMCP until it has enough context to answer the question.
Hope this helps.
Earlier quoted context omitted.
Same here. Can't we just give the repo URL in Cursor/Windsurf to use the search tool to get the context? :thinking:
Yeah this is one fundamental reason I don't see MCP taking off. The only real use cases there are will just be built in natively to the tools.
E.g. one of the biggest annoyances for me with cursor was external documentation indexing, where you hand it the website of a specific libarary and then it crawls and indexes that. That feature has been completely broken for me (always aborting with a crawl error). Now with a MCP server, I can just use one that is specialized in this kind of documentation indexing, where I also have the ability to tinker with it if it breaks, and then can use that in all my agentic coding tools that need it (which also allows me to transfer more work to background/non-IDE workflows).
> 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…
> 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]