Just checking if I’ve missed a post about this? Claude Code using the MCP can create workflows using the Supabase tavle views now but it’s visibility is very limited and it can’t create/edit them. It’s looking at my Supabase schema to get info about the tables rather that the table views right in WeWeb because it can’t see them.
“On “backend module isn’t installed”: that’s WeWeb’s own server-side layer, separate from Supabase. Your Table Views exist and work fine at runtime — fetch-table-view is running in all these workflows. What’s gated is the MCP introspection tooling: listTableViews, getSupabaseProjectTables and getIntegrationSkill all need that module, which is why I couldn’t enumerate your views and had to infer 608213a2 = spaces and 32ef84ea = beds from the old workflows. It’s also why I read your schema through the Supabase MCP instead. Nothing is broken; I just can’t see as much as I’d like. Installing it would also unlock backend workflows and API endpoints.”
Claude is telling be to “install the backend module” but when i click this my WeWeb tries to open weweb backend which I’m worried will interfere with my Supabase as a backend through the integration??
*
"On the backend module — I can’t install it, only you can. The MCP tool just returns a link that performs the install when you open it in the editor:*
I generated it with auth and storage deliberately switched off, against the tool’s defaults. Two reasons: you’re on Supabase auth, and installing WeWeb’s auth module can scaffold its own sign-in / sign-up / reset-password pages into the project — which would collide with your existing Auth pages and the tenant_id / get_current_tenant_id() situation. Storage is similarly unused. That URL installs the backend module only.
Worth knowing before you click: the tool notes that once the backend is installed, this tool can’t add auth or storage later — you’d enable them manually in the editor. So backend-only now doesn’t paint you into a corner, it just means a manual step if you ever want the others.
What it unlocks: listTableViews and getSupabaseProjectTables (so I could stop inferring which view is which), plus backend workflows and API endpoints."