[johnjungles]

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!

[cloudking]

What is unique about your solution? Are you essentially handling auth tokens for the user to interface MCPs with external APIs?

[johnjungles]

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.