You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this Supabase MCP Server is steadily growing (thanks to everyone who tried it 💥, raised issues ❤️, submitted PRs 🔗) I think some organization and communication about the future of the project is in order.
Context
I started this project several weeks ago, so it's still quite new, evolving and has lots of exciting things ahead of it. I am focusing on improving it as rapidly as I can (I have a full-time job) while keeping ensuring stability of the system.
I am publishing this roadmap here because I want to gather feedback, ideas, requests from you (users) - so if you see (or don't see) something you like - please do let me know!
v0.4 Roadmap
The goals for the next release are:
improved safety: MCP is a powerful tool but it can easily destroy your database. I really want to help you avoid that.
improved tool reliability: some of the most useful tools are currently not reliable due to imperfect implementation. I want to focus on improving the reliability of tool calls, specifically around getting the API and SDK specs
solid infrastructure: I am still learning and this is my first open-source project getting some levels of attention so I want to ensure it has solid foundations to be able to grow and develop. Additionally, if this picks up further I would want to make a paid version which would require a solid infrastructure / tooling.
The list below holds some of the biggest changes I want to bring, but it's by no means exhaustive or set in stone:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there 👋!
Since this Supabase MCP Server is steadily growing (thanks to everyone who tried it 💥, raised issues ❤️, submitted PRs 🔗) I think some organization and communication about the future of the project is in order.
Context
I started this project several weeks ago, so it's still quite new, evolving and has lots of exciting things ahead of it. I am focusing on improving it as rapidly as I can (I have a full-time job) while keeping ensuring stability of the system.
I am publishing this roadmap here because I want to gather feedback, ideas, requests from you (users) - so if you see (or don't see) something you like - please do let me know!
v0.4 Roadmap
The goals for the next release are:
The list below holds some of the biggest changes I want to bring, but it's by no means exhaustive or set in stone:
Feel free to share your thoughts and thanks for reading!
Beta Was this translation helpful? Give feedback.
All reactions