Posted by liadyo 4/3/2025
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.
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.
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.
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.
MCP is REALLY taking off FAST D:
$ curl -L https://gitmcp.io -v
< HTTP/2 308
< date: Sat, 05 Apr 2025 20:56:33 GMT
< content-type: text/plain
< location: https://gitmcp.io/
< refresh: 0;url=https://gitmcp.io/
...
* Connection #0 to host gitmcp.io left intact
* Maximum (50) redirects followed
curl: (47) Maximum (50) redirects followed
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.