🚀 MCP support, improved Supabase Select, formula columns, and more!

[Tamara]

Hey everyone

This week’s release brings MCP support, a redesigned Supabase Select experience, formula columns in table views, expanded AI element support, and more!

Check out the details below

MCP support: build in WeWeb with your AI tool of choice

If you love leveraging AI tools like Claude Code, Codex, or Gemini to build apps, you can now connect your preferred AI setup to WeWeb and let it work directly on your project:

Here are just some of the things you can use it for:

Build complete features from a single prompt: need to add an onboarding flow or pricing cards? Describe the feature you want and let your AI tool implement it across your project.

Clean up and optimize existing projects: use MCP to review workflows, identify redundant logic, standardize naming conventions, reorganize structures, and simplify your application architecture.

Turn designs into working UIs: have a Figma file, mockup, or screenshot? Your AI tool can use MCP to recreate layouts, pages, interactions, and application structures directly in WeWeb.

Create custom components: need functionality that doesn’t exist out of the box? With MCP, your AI tool can generate coded components and add them directly to your WeWeb project.

And these are only a few examples. There are countless ways to use MCP to build, maintain, and evolve your WeWeb projects.

Check out the release notes for a step-by-step tutorial and more details

Configure Supabase Select more easily

The Supabase Select action has been redesigned to make query setup clearer and more complete in the Editor.

The action panel is now organized into dedicated sections:

• Filters
• Sorting
• Pagination
• Advanced

This makes it easier to configure Supabase queries in one place, especially when working with related tables and filtered results:

Add custom columns to WeWeb Users tables

You can now add columns directly to WeWeb Users tables:

Extend user records with additional information that fits your app’s needs

Add custom user properties such as roles, onboarding status, internal notes, preferences, subscription metadata, or profile-related fields

Add calculated fields to WeWeb table views

You can now add and edit formula columns to table views:

Formula columns let you calculate and display dynamic values in your table views without creating a new database column!

Create more elements with WeWeb AI

AI can now help you build and configure more parts of your app faster, with new support for:

• Timeline
• Chat AI
• Chat

We’ve also improved AI usage for several existing elements, including Datagrid, Select, and Input mask.

Other improvements and fixes

• JSON column data can now be inserted with the Insert row action
• Table configuration is now retrieved more reliably in the Editor when inserting or updating rows
• Workflow action results no longer incorrectly display as “Mission result (action deleted)”
• Incorrect Cognito provider setup no longer causes the server to stop working
• Resolved a database migration issue affecting projects switching from WeWeb Auth to Supabase Auth
• Xano tables now better handle addon data, removed data, and addon name updates
• Table descriptions are now saved correctly

Check out the release notes for more details

As always, let us know what you think

[thomlov (Thomas Løvdahl)]

So exited to try the new mcp. And you guys waited til the day I went on vacation

[Tamara]

Haha

Hope you enjoy the vacation! No worries, MCP will still be here when you’re back, and we’d love to hear what you think!

[Hugo-OC]

Hey,

First of all amazing work with that update !

I am really having a great time playing around with the MCP. I have a few questions:

• Do you plan to expose project management endpoints? (My use case is that I have a template project where I spin up an instance per client, so I would like to automate provisioning for new clients).
• From my understanding, the MCP can’t access legacy collections. Are there any plans to support this in the future?

Thank you !

[Tamara]

Hey Hugo

Glad to hear that you like the MCP!

Just to make sure I understand your use case correctly: when you say “project management endpoints,” are you thinking about things like duplicating or creating projects from a template, then configuring project settings, environment variables, and data sources for each new client?

[akram]

The one I’ve been impatiently waiting for MCP! And a really cool surprise that this initial iteration goes way beyond custom components.

Already had a few runs with it to audit and fix a few issues systematically that I was too lazy to dive into myself directly, and it works amazingly well.

I second Hugo’s question regarding the legacy (interface) collections, as well as the interface plugins (namely the supabase ones), is there a plan to support those, too?

Thanks!

[Tamara]

Happy to hear that you like it!

@Hugo-OC @akram Regarding the legacy collections and plugins, they aren’t currently planned for MCP support.

That said, Supabase support is on our radar: we’re planning to support the Supabase integration in the coming weeks.

[Hugo-OC]

Hey,

Here I only had in mind the duplicating a Weweb project part but I mean the rest is interesting too.

I also noticed that the MCP was unable to save workflows with a custom trigger (on custom coded components), is that a bug or a feature to come ?

[Tamara]

Hey Hugo

For duplicating a WeWeb project via MCP: this isn’t available yet, but it’s definitely something we plan to support in the coming weeks.

For the workflow issue with a custom trigger from a custom-coded component: that sounds like a bug. Could you please create a support ticket with the details so the team can investigate properly?

[Batik_Okazov]

Some of the most important updates we’re all looked for. Thank you

[MrUnfreeze (X)]

Congratulations to the team, it’s brilliant work. I already love it!

[jefeOliveira]

Next please:

• CRON jobs / scheduling backend functions
• Ability to rename columns / edit data types
• Cascade table actions

[Yaj]

I’ve also noticed we can’t see component workflows etc. Was a bit disappointing to see an MCP released and I wasn’t even able to use it for the work I was doing cause it’s missing a bunch of features for older content. I understand why we’ve got all the weweb backend stuff implemented already but that feature is so fresh compared to reuseable components and collections.

I had to go back to my own method of working with agents and weweb since the MCP doesn’t expose enough of the project.

[Tamara]

Hey Yaj

Thanks for the feedback!

Could you please tell me which component workflows are missing?

[Himanshu (Himanshu Sharma)]

Looks promising and seems to create the UI as expected. Will try how the backend works.

Can we please increase the auth session limit for the MCP? I had to authorise it for a second time in a day

[Tamara]

Hey Himanshu

Glad to hear the UI generation worked as expected!

On the MCP auth session limit: I’ll share it with the team.

[arjun_anand (Arjun)]

Hey team,

Amazing feature! Thanks for the release. As with the people above - do wish I was able to use legacy xano blocks (xano request, fetch collection, etc). At the moment seems like I can work around it by creating a workflow for just that function manually and have the MCP use that, but hopefully this is on the radar to allow.

[ekneba (Elliot)]

Here’s a Claudeacious summary of my experience so far. I’m enjoying the increased functionality but have hit some stumbling blocks. Just sharing for your/the community’s info

Context: using the MCP (via Claude/Opus) to make surgical edits to an existing, complex app backed by an external database (Supabase data source, no WeWeb native backend). Greenfield page generation worked well; the gaps below show up in editing-existing-apps and external-data scenarios.

Missing / unavailable

• Data-layer tools don’t work when the data source is an external DB (Supabase/Xano) rather than WeWeb’s native backend. listAllWeWebTables, searchTableViews, listTableViews, fetchTableViewData, and the table-creation tools all return “WeWeb backend is not installed” / “DB_NOT_SETUP”. There’s no MCP path to read, create, or even fetch data from integration collections — so the entire data layer requires an editor/WeWeb-AI detour. (Request IDs available on request.)
• No way to read an element’s workflow/action detail. getPageSemantic shows that a click workflow exists and lists dependency UIDs, but not the action steps or their bound parameter values — so you can’t inspect how an existing RPC/action call is configured via MCP.
• getPageSemantic doesn’t expose binding/filter expressions. It shows BINDED TEXT / REPEAT ON SLOT + dependency UIDs, but not the literal formula — so the content of a mutation (e.g. whether a repeat’s filter is correct) can’t be verified via MCP, only in Preview.
• No reliable targeted/per-element read. getPageElementsByUid returns stale data (kept returning an element after it was deleted), so the only trustworthy read is the full getPageSemantic, which is heavy on large pages.
• No MCP way to force an external schema re-introspection when a view/table definition changes.

Friction / bugs

• deleteSection is unreliable — fails to match a section that addSection just created (“not found in semantic representation”); deleteElement on the same UID works. Sections added via the API appear to register as ww-div.
• The MCP session doesn’t persist the active project/workspace across turns — every turn starts “no workspace selected” and requires re-running switchProject first.
• Stale schema surfaced as current — a collection bound to a recently-redefined view exposed an old field set (phantom fields, missing new ones), and the AI reported the stale shape as fact; only caught by cross-checking the DB directly. Required a manual schema refresh in the editor.
• Binding-path discoverability — content.default.text is rejected (only the language key, e.g. content.default.text.en, can be bound). Correct behaviour, but not obvious from the data-access docs.

Worked well

• Element-layer writes are solid and verifiable: addSection, addElements, editElement, editRepeat all sync correctly and confirm via getPageSemantic.
• getPageSemantic is authoritative for tree structure.
• The dataAccess docs give exactly the right binding paths.

Highest-impact ask: make the data-layer tools work for external-DB (Supabase-backed) projects — read collections, fetch their data, manage collection filters. That’s the one gap that blocks true full-stack MCP on the most common WeWeb stack.

[ericp (Eric Poortinga)]

I haven’t connected the MCP yet with Claude, but am I reading the comments correctly that it won’t work with the traditional Xano plugin and related collections?

[Tamara]

Hi Eric

The legacy collections and plugins aren’t currently planned for MCP support.