61–67 of 67 posts
I want to change this to gitmcp.io. I directly modified it to: https://gitmcp.io/modelcontextprotocol/servers/tree/main/src...
But it doesn't work in Cursor. Even if I point to the index.ts file, it still doesn't work. Can anyone tell me how I should write it?
Not sold on MCP being the right paradigm (we'll see), but had a lot of fun building an MCP server recently using https://github.com/tadata-org/fastapi_mcp to quickly get up and running and be able to call to it from Cursor.
$ curl -L https://gitmcp.io -v
https://gitmcp.io/
https://gitmcp.io/
...
* Connection #0 to host gitmcp.io left intact
* Maximum (50) redirects followed
curl: (47) Maximum (50) redirects followed
Earlier quoted context omitted.
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.
There's always a baseline expectation of some kind of shared context, sure, and within that kind of context your comment makes total sense. But all of the stuff I'm pointing out is definitely not part of any notion of that kind of shared context. That's my whole point!
If you give a lecture to 100 people, and 5 people leave that lecture confused, that's their problem. But if 95 people leave that lecture confused, that's your problem.
Some context. 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…