If you want to try out mcp (model context protocol) with little to no setup: I built https://skeet.build/mcp where anyone can try out mcp for cursor and dev tools. We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support you have no idea how hard it is to set up SSE, deal with API keys and scope issues, and then to find things like the tool that you want isn’t even coded yet. And so one of the areas we found it to be useful was to do the soft communications with tools like Jira linear slack - updating stakeholders and all that friction that engineers hate doing. Some other areas people use a lot of tools with sequential thinking Mostly for workflows that I like: * start a PR with a summary of what I just did * slack or comment to linear/Jira with a summary of what I pushed * pull this issue from sentry and fix it * Find a bug a create a linear issue to fix it * pull this linear issue and do a first pass * pull in this Notion doc with a PRD then create an API reference for it based on this code * Postgres or MySQL schemas for rapid model development Everyone seems to go for the hype but ease of use, practical pragmatic developer workflows, and high quality polished mcp servers are what we’re focused on Lmk what you think!

Mostly give them up to date documentation about the stack they're using, so they can consult tools instead of hallucinate stuff.

On using MCP servers with Claude: It's actually been kind of annoying. Sometimes I just need a quick script to copy/paste and it tries to connect to a GitHub repo or write to a local file even when I specify I don't want those things. Overall they're the behavior when using them is wildly inconsistent when I use them. It's annoying I have to manually shut off the MCP servers to get what I want.