u/Potential-Art7696

Hi everyone, I’m the solo developer behind UluP Spaces, and I’m currently working on an MCP integration for it, so I wanted to share what I’m building and get feedback from people who actually work with MCP.

UluP Spaces is a visual project workspace. Instead of having a project represented only as a flat task list, you build it as a canvas made of nodes.

Each node represents a part of the project and contains its own tasks. Tasks can have notes and files, and the node automatically reflects its completion progress.

There are also focused task workspaces, search across nodes and tasks, collaboration with viewer/editor roles, real-time updates, and a presentation mode that lets you walk through the project node by node.

One of the features I'm currently working on is MCP.

The direction I'm exploring is allowing an AI agent to actually understand the structure of a project rather than only receiving isolated pieces of information.

For example, an agent could potentially inspect the project's nodes and tasks, answer questions about the current state of a project, create new tasks or nodes, update existing ones, or help turn a specification into a project structure.

I'm deliberately still working out the right boundaries for this. I don't want an agent to have unrestricted access just because an MCP connection exists.

So I'd really like feedback from people who are already using MCP:

What would you actually want an AI agent to be able to do inside a visual project workspace?

And just as importantly, what would you absolutely not trust an agent to do automatically?

I'm the developer behind UluP Spaces, so this is a genuine showcase of something I'm currently building rather than an unrelated discussion about MCP.

https://www.ulupspaces.com/

I didn't start UluP Spaces as a SaaS.

About 4 years ago, I started making indie games just because I loved gaming. My first project was Five Nights at Saul's, a parody horror game inspired by FNAF and Better Call Saul/Breaking Bad. I had basically no development background. I downloaded FNAF 2 assets, cut them manually in Photopea, learned Clickteam Fusion through YouTube tutorials and even experimented with some of the first rough AI voice cloning tools.

Then I lost the entire original project.

Instead of giving up, I rebuilt it from scratch. Around the time the first version of ChatGPT came out, I started using it step by step for debugging, logic and development. That eventually became a much bigger sequel with three offices, more complex AI and an Android port, which got thousands of views on Game Jolt.

Then, in February 2026, I wanted to build something completely different.

I started UluPProject, a social network I built alone with Bubble.io, manually implementing everything while following AI instructions and figuring things out as I went.

By April, it was fully functional. Users could create profiles, including anonymous ones, post photos and thoughts on a global feed, create communities that were approved by the admin, join other communities, share messages, photos, videos, audio and downloadable files, and privately chat with other users.

The original idea was a social network based around mutual help, where users could eventually earn money based on their contributions.

It actually worked. But then reality hit: I'm one person. Moderation, storage, file management, security, scaling and everything else involved in running a social network was simply too much.

My friends used it for a while mostly for fun, and eventually I shut it down.

But I didn't consider it a failure.

I realized that the part I actually cared about wasn't the social network. It was the idea underneath it: people coming together, sharing information and collaborating.

So I kept that idea and completely changed its purpose.

That became UluP Spaces.

On July 31, 2026, I launched it. This time I designed the flows on paper first, moved away from my previous no-code approach and built a proper backend and SQL database with Supabase. I spent days and nights working on the UI, UX, database relationships, permissions and release security...

Then GitHub suddenly suspended my account. Luckily, because I had kept the architecture clean and maintained backups, I was able to recreate the Supabase database and get the project running again surprisingly quickly.

UluP Spaces is now a visual workspace where you can map projects and ideas on a canvas, break them into nodes and tasks, collaborate with other people and share projects publicly.

About 18 days after launch, I saw a huge spike in traffic: 154 visitors (+2,500%) and 726 page views (+2,000%) in the analytics period.

And instead of celebrating for too long, I went straight back to coding.

I'm currently experimenting with MCP (Model Context Protocol), with the idea of making UluP Spaces useful not only for humans, but also as a visual workspace for AI agents and development workflows.

Looking back, it's strange.

A horror game became a social network. The social network failed. But the idea underneath it survived, and that idea became a SaaS product.

That's probably the biggest lesson I've learned from building alone:

Sometimes you don't need to save the product. You need to save the idea that was worth keeping.

If you're also building a SaaS alone, I'd love to hear about a project you completely changed direction on.

It started as a horror game.

About 4 years ago, I was making indie games with basically no development experience. I learned by watching YouTube tutorials, cutting assets manually in Photopea and figuring things out as I went.

Then I started using AI to help me understand code and debugging.

Fast forward to February 2026: I decided to build a social network on my own.

I spent two months building UluPProject with Bubble.

Profiles, communities, private chats, a feed, photos, videos, audio and downloadable files.

It actually worked.

The problem?

It was completely insane to operate alone.

Moderation, storage, security, scaling... eventually I shut it down.

But I kept one thing from it:

the idea of people coming together around something and collaborating.

So I rebuilt the idea from scratch.

Different architecture. Different purpose. Different product.

That became UluP Spaces.

I launched it on July 31.

Today it's a visual workspace for mapping projects, ideas and workflows on a canvas.

And now I'm experimenting with MCP and AI agents.

Looking back, it's weird to realize that the thing I'm building today is connected to a horror game I made four years ago.

I guess solo building isn't really a straight line.

It's more like a bunch of failed projects slowly turning into the next one.

What was the weirdest project you built before finding what you're working on today?

link to studio: https://www.ulupstudio.com

I’ve been working on a new part of UluP Spaces: Community Templates. The idea is to let a project become something other people can build from.

When you create a project in UluP Spaces, you can submit it as a template. After a review, if it's approved, it becomes part of the Community Templates section.

From there, other users can:

• explore the template
• preview its structure and nodes
• use it as a starting point for a new project
• vote for it

The most appreciated templates will eventually also be featured on UluP Studio.

I like the idea of a project not ending when you're done with it. A useful structure you've created for yourself could become a starting point for someone else's work.

Still building this out, but I'm curious: would you submit one of your own project structures as a template for other people to use? ulupspaces.com

Most tools give you a flat list, or a whiteboard that gets messy past 20 items. I built UluP Spaces trying to solve both — here's the full breakdown, not just the pitch.

Structure: Create a project — from scratch, from a built-in template, or from one shared by another user in the community library. Inside, you create nodes, each one a piece of the project. Add tasks inside a node: two tasks, complete one, the node hits 50%. Complete both, it turns green at 100%.

Focus Mode: Click any task and you're in its own focused space — notes, a Pomodoro timer, file attachments, all scoped to that one task.

Scale: Every node holds unlimited tasks. Every task holds its own notes/files. Unlimited nodes per project, unlimited projects. I've actually stress-tested this myself up to 100 nodes in one project and kept it fluid — tested and optimized, not just theoretical.

Present Mode: Turns the whole map into a walkthrough — arrow keys or mouse click to move node to node, each one previewing its tasks as you go. Built specifically so a project can explain itself to someone who wasn't there when you built it. **Search**: Finds specific tasks and nodes across a project, not just node names.

Sharing (UluP Share): One click turns any project into a public, read-only page — no login required to view it. Pages are properly indexed (own SEO setup), and public profiles now have their own searchable page too. For example, here is the link to my share page showing how I built the app in the first 11 days after its release: https://www.ulupspaces.com/share/3667026b-da12-410e-9e25-c943142539b1

Collaboration: Invite links, real member roles (viewer vs editor), real-time updates when someone else moves something.

Community templates: Anyone can submit a project as a reusable template — reviewed before going live, now with voting so the best ones surface. Solo developer, built and tested all of this alone. Happy to go deeper on any piece, or hear where this breaks down for how you'd actually use it. ulupspaces.com

Most tools give you a flat list, or a whiteboard that gets messy past 20 items. I built UluP Spaces trying to solve both — here's the full breakdown, not just the pitch.

Structure: Create a project — from scratch, from a built-in template, or from one shared by another user in the community library. Inside, you create nodes, each one a piece of the project. Add tasks inside a node: two tasks, complete one, the node hits 50%. Complete both, it turns green at 100%.

Focus Mode: Click any task and you're in its own focused space — notes, a Pomodoro timer, file attachments, all scoped to that one task.

Scale: Every node holds unlimited tasks. Every task holds its own notes/files. Unlimited nodes per project, unlimited projects. I've actually stress-tested this myself up to 100 nodes in one project and kept it fluid — tested and optimized, not just theoretical.

Present Mode: Turns the whole map into a walkthrough — arrow keys or mouse click to move node to node, each one previewing its tasks as you go. Built specifically so a project can explain itself to someone who wasn't there when you built it.

Search: Finds specific tasks and nodes across a project, not just node names.

Sharing (UluP Share): One click turns any project into a public, read-only page — no login required to view it. Pages are properly indexed (own SEO setup), and public profiles now have their own searchable page too.

Collaboration: Invite links, real member roles (viewer vs editor), real-time updates when someone else moves something.

Community templates: Anyone can submit a project as a reusable template — reviewed before going live, now with voting so the best ones surface. Solo developer, built and tested all of this alone. Happy to go deeper on any piece, or hear where this breaks down for how you'd actually use it. ulupspaces.com

Sto cercando di capire quale sia il modo migliore per organizzare un esame particolarmente grande.

Personalmente mi trovo abbastanza bene con una struttura visuale: argomento principale → sottoargomenti → cose da studiare → materiale e appunti collegati.

Il problema delle classiche to-do list è che dopo un po' mi sembra di avere davanti solo una sequenza infinita di cose da spuntare e faccio fatica a vedere i collegamenti tra gli argomenti.

Per esempio, per Diritto Privato avrebbe più senso per voi avere:

Diritto Privato
→ Obbligazioni
→ Contratti
→ Responsabilità
→ Diritti reali

con le singole cose da studiare dentro ogni argomento?

Oppure preferite una semplice lista tipo:

☐ Studiare obbligazioni
☐ Studiare contratti
☐ Ripassare responsabilità
☐ ...

Sono curioso soprattutto di sapere come vi organizzate voi durante la sessione, perché sto cercando di trovare un metodo che non diventi ingestibile quando gli argomenti sono tanti.

Each node in the map is a version shipped (v1.5, v1.6, v2.0, v2.1), each task is something real that happened. Present Mode walks through it automatically. https://www.ulupspaces.com/share/3667026b-da12-410e-9e25-c943142539b1 Built solo. Curious what people think of using a product to demo itself like this.

Hi everyone,

I've been building UluP Spaces, a visual workspace for organizing projects as connected maps.

The idea came from a simple problem: when projects become complex, traditional lists and folders often hide the bigger picture. You have tasks, notes, files and ideas, but they feel disconnected.

With UluP Spaces, projects are built as visual maps: nodes represent different parts of a project; each node can become its own focused workspace with tasks, notes, files and progress; projects can be shared and explored through a community with reusable templates.

I'm still improving it and I'm not looking for a sales pitch here;I would genuinely love feedback from people who use PKM systems.

Do you think visual project maps could fit into a personal knowledge management workflow? What would you add or change?

Thanks!

I’ve been working on UluP Spaces for a while now, and lately, I realized that the friction of navigating through endless menus to find specific projects was killing my flow.

I’m currently redesigning the whole link structure to make workspaces feel like "first-class citizens" in the app,cleaner, faster, and instantly accessible via direct links.

I’m still in the middle of the refactor, but I wanted to share a look at where the UI is heading.

Hi everyone,

I wanted to share the story behind something I've been building.

My name is Emanuele, I'm a 20-year-old creative from Italy. Since I was young I've always had different passions: acting, writing, storytelling and technology.

For a period of my life I was working as a bartender, but I always felt I wanted to create something of my own.

I once tried to enter the IT world, but during a conversation I was told something that stayed with me: maybe my strength wasn't only the technical side, but my creativity.

That pushed me to think about what I really wanted to create.

I imagined a social platform where people could help each other, collaborate and turn their ideas into reality.

The problem was that I didn't know how to build it. The person who I hoped could help me develop it couldn't continue with me, and I was left with an idea but no technical skills.

Instead of abandoning it, I decided to learn.

After two months of studying and experimenting, I built the first version of that social network by myself. It wasn't perfect, but it proved something important to me: you don't always need someone else to give your ideas a chance.

That first experiment became the foundation of UluP Studio.

Today I'm rebuilding that vision with a stronger philosophy:

UluP Focus: helping people organize their goals and focus

UluP Spaces: creating spaces where people with similar ambitions can collaborate and build together

My goal isn't just to make another app. I want to create a place for creative people who want to start something and don't want to keep their ideas only in their heads.

I'm still at the beginning, but this is my journey of building something from zero

Hi everyone,

I wanted to share my journey of learning technology by building a real project.

I started without a traditional IT background. I had an idea for a platform focused on collaboration and productivity, but I didn't have the skills to build it.

Instead of abandoning the idea, I decided to learn and experiment by myself.

During this process I moved from no-code experiments to building with modern web technologies:

Next.js

Supabase

Vercel

authentication and database management

The project evolved into UluP Studio, where I'm exploring ideas around productivity tools and collaborative spaces.

The biggest lesson for me has been that building something real teaches you things that tutorials alone can't.

For people working in IT: what advice would you give to someone transitioning into the field through self-learning?