Show HN: GitMCP is an automatic MCP server for every GitHub repo

#1

Post by liadyo » Thu, Apr 03, 2025, 6:28 PM UTC

Show HN: GitMCP is an automatic MCP server for every GitHub repo
gitmcp.io

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#2

Post by liadyo » Thu, Apr 03, 2025, 6:28 PM UTC

We 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

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#3

Post by lukew3 » Thu, Apr 03, 2025, 6:38 PM UTC

Cool project! I would probably call it an MCP server for every Github repo though since project could be confused for Github Projects which is their work planning/tracking tool.

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#4

Post by the_arun » Thu, Apr 03, 2025, 6:40 PM UTC

But why would we need an MCP server for a github repo? Sorry, I am unable to understand the use case.

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#5

Post by qwertox » Thu, Apr 03, 2025, 6:43 PM UTC

That is a complex webserver. https://github.com/idosal/git-mcp/tree/main/api

What about private repos in, let's say GitLab or Bitbucket instances, or something simpler?

A Dockerfile could be helpful to get it running locally.

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#6

Post by liadyo » Thu, Apr 03, 2025, 6:46 PM UTC

the_arun wrote: post #4

But why would we need an MCP server for a github repo? Sorry, I am unable to understand the use case.

It's very helpful when working with a specific technology/library, and you want to access the project's llms.txt, readme, search the docs, etc from within the IDE using the MCP client. Check it out, for exmaple, with the langgraph docs: https://gitmcp.io/#github-pages-demo It really improves the development experience.

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#7

Post by liadyo » Thu, Apr 03, 2025, 6:48 PM UTC

qwertox wrote: post #5

That is a complex webserver. https://github.com/idosal/git-mcp/tree/main/api What about private repos in, let's say GitLab or Bitbucket instances, or something simpler? A Dockerfile could be helpful to get it running locally.

Yes, this is a fully remote MCP server, so the need for an SSE support makes the implementation quite complex. The MCP spec updated to use HTTP streaming, but clients do not support it yet.

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#8

Post by TechDebtDevin » Thu, Apr 03, 2025, 6:54 PM UTC

liadyo wrote: post #7

qwertox wrote: post #5

That is a complex webserver. https://github.com/idosal/git-mcp/tree/main/api What about private repos in, let's say GitLab or Bitbucket instances, or something simpler? A Dockerfile could be helpful to get it running locally.

Yes, this is a fully remote MCP server, so the need for an SSE support makes the implementation quite complex. The MCP spec updated to use HTTP streaming, but clients do not support it yet.

Gemini does I believe. On my list of todos is to add this to my fork of mcp-go.

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#9

Post by liadyo » Thu, Apr 03, 2025, 6:54 PM UTC

lukew3 wrote: post #3

Cool project! I would probably call it an MCP server for every Github repo though since project could be confused for Github Projects which is their work planning/tracking tool.

Thanks!

Re: Show HN: GitMCP is an automatic MCP server for every GitHub repo

#10

Post by pfista » Thu, Apr 03, 2025, 7:14 PM UTC

Do you auto-generate specific MCP tools for the repo? Curious what the queries you would use with an AI agent to get a response back.

I'm building my own hosted MCP solution (https://skeet.build) and have been deliberately choosing which tools to expose depending on the use case- since there are tool limits due to the context window for apps like Cursor.