If anyone is having trouble with outdated context or depreciated code generation my team and I are building an MCP to augment Cursor!
We are two weeks in and already scraping 10’s of thousands of documentation pages and organizing it into a knowledge graph for models like Claude to use!
Already at 5k waitlsts! Sign up for updates, and would appreciate any feedback and support!
Sounds awesome! Organizing documentation into a knowledge graph sounds like a game-changer for keeping models up to date. Signed up—looking forward to seeing how it evolves!
Could you share a bit more about your planned Cursor integration and data?
Data on your website is partially outdated. Is there a reason you do not list the docu versions?
MCP might not be the way to go as in Cursors MAX the mcp call costs 1 full request price in USD. How would your integration work to avoid that?
Given that there is a waitlist of 5k users, is there a point in signing up for the waitlist as its unclear when you will get around to add those users.
Also 10s of thousands of docu pages doesnt say much. will users be able to add docu they need? or who chooses what you will add?
Hey thanks for your interest!
We are still developing our product, so things will be updating quickly!
We will listen to users! If MCP isn’t the way to go for this sort of thing, we are open to working with cursor to integrate with our API, or provide a sort of Real-Time model endpoint for users to choose!
We will add users in big waves! So please sign up still, promise we will roll this out quickly!
Yes! We have scraped nearly 400K docs! And users will be able to request documentation that isn’t available to be scraped!