Building https://check.supply: the easiest way to mail a real paper check from your iPhone. Link your bank, type the amount, and we print + mail it for you — with optional certified or express USPS tracking
Maybe we should have models govern models to prevent models from going haywire and falling into a loop of a repetitive pattern or influencing society towards swarm like behavior patterns
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!
Building a tool to supercharge your Cursor, Windsurf, Claude and other developer tools by connecting it to polished, high quality mcp servers for linear, slack, DBs, and other useful workflows.
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!
Currently working on a desktop app so everything runs on a native Mac app!
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
I built https://skeet.build which lets your connect your favorite tools via mcp to Cursor. We focus exclusively on developers and dev tools to build high quality “it just works” experiences for mcp because we found that community mcp quality is low, many mcps were not useful for devs, and SSE remote mcp took a lot of effort to get it to a point where it’s reliable and working well.
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 now OpenAI agents!
We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support and complexity trying to stand up your own.
Mostly for workflows 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
I actually think that most problems that took 5-20 mins are now a few minutes and it’s more about how many of those intense minutes and loops you’re going through.
Also, right now engineers are hyper optimized in the code aspects but not thinking about the context into cursor and context out of cursor.
Like the amount of copy paste from Notion / JIRA / Sentry and the amount of output like summarizing the git commits and PRs, slack and other “over communication” you have to do these days. This is the area I think we can more easily automate away.
I too am working on effortless mcp servers for other developers using cursor and windsurf - there’s so much out there on mcp but turns out a lot of mcp servers don’t “just work”. A lot of other people have been porting APIs but actually you need to put a lot more thought into it because people don’t memorize uuids that are required to make api calls. Memory is a good approach, but afraid of the recall aspect and how that could potentially cause tool calls with bad inputs.
I built https://skeet.build where anyone can try out mcp for cursor and windsurf - we approached it with just brute force thoughtful design and a lot of trial and error.
We did this because of a painpoint I experienced as an engineer having to deal with Jira and Linear - updating slack and all that friction. I noticed I copy and paste a lot to cursor and so spent time building this app.
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
So I built https://skeet.build and something’s that I learned along the way:
1. Yes MCP is basically an api wrapper and function calling. However if you “just” port open api v3 specs then you get really weird results like (sorry I can’t move you linear ticket because you need the uuid of the todo and in progress workflow ids). Basically people don’t memorize uuids of the APIs. APIs weren’t designed for natural language so there’s a lot of work that needs to be put in in order for it to “just” work.
2. MCP is still in early days. There’s a lot of community mcp servers but more than half of them don’t actually work. Also you have to setup your own oauth, go get your own keys, read docs on auth because some authenticate at the app level not on user level and make sure the urls are correct. So even though everyone is posting about how easy it is to build your own mcp servers it’s actually a lot of friction.
3. SSE setup is trickier than you think. Remote mcp is something they’re working on still. SSE requires a lot of low level networking, load balancer time out tuning, heartbeats, etc to get things working reliably. Sure it works for your local machine for that 30 mins but to get it working scalably and reliably on cloud infrastructure is really hard and not yet proven out yet.
I built https://skeet.build where anyone can try out mcp for cursor and dev tools without a lot of setup.
I build APIs for my day job and mcp isn’t the same as just porting over APIs.
I did this because of a painpoint I experienced as an engineer having to deal with Jira and Linear - updating slack and all that friction. I noticed I copy and paste a lot to cursor and so spent time building this app.
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
• connect to Postgres and build CRUD api from the table schema
• pull this issue from sentry and 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 codebase, then create a new Notion page with the reference
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
I built https://skeet.build where anyone can try out mcp for cursor and dev tools without a lot of setup.
We did this because of a painpoint I experienced as an engineer having to deal with Jira and Linear - updating slack and all that friction. I noticed I copy and paste a lot to cursor and so spent time building this app.
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
• connect to Postgres and build CRUD api from the table schema
• pull this issue from sentry and 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 codebase, then create a new Notion page with the reference
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
So there’s a lot of noise about MCP but it’s just a tool - we found that we’re solving for developer workflows (where there’s pain). People want to get shit done but after coding to update JIRA tickets just kills momentum.
We just make it a highly reliable, easy to use, after committing - add a comment with a summary to that Jira/linear issue. Start a PR in GitHub and assign x, update the slack channel with an update.
In order to get this it wasn’t about porting APIs to mcp. It was thoughtfully designing and optimizing for these workflows. Also quality and polish where the calls are highly reliable - required lower level networking optimizations, sessions, etc to make to work smoothly.
But yes, also part of the frictionless experience was, just oauth.
I built https://skeet.build where anyone can try out mcp for cursor and dev tools without a lot of setup
Mostly for workflows 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 - 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 codebase, then create a new Notion page with the reference
MCP tools are what the LLM uses and initiates
MCP prompts are user initated workflows
MCP resources is the data that the APIs provide and structure of that data (because porting APIs to MCPs are not as straight forward)
Anyways please give me feedback!