Plugin actions and WeWeb MCP

The WeWeb MCP server does not expose plugin actions, so an AI agent connected over MCP cannot create or edit a workflow step that uses one. If your project relies on a plugin such as Xano or Supabase, your agent will not be able to build with those plugin actions.

Use Integrations instead

Integrations are the supported path, and the MCP does expose ways for your AI to build using integration actions. If your provider has one (Xano and Supabase both do), we recommend switching to it. Your agent can then create and edit those actions like any other part of your project.

See all available Integrations →

Workaround for plugin actions

If you are stuck on plugins for now, some users use the makeshift workaround below. It is not an official MCP feature. Treat it as a temporary bridge, and review every workflow carefully before you rely on it.

How the workaround works

In WeWeb, a workflow is stored as JSON. When you copy a workflow in the editor, WeWeb puts that JSON on your clipboard, which allows you to paste it as a new workflow in the WeWeb editor.

However, if you try to paste it into a text field, then you will see the raw JSON (which opens up the potential for you to make direct edits to the JSON).

If you already have workflows that use the plugin actions you care about, you can give that JSON to your MCP-connected AI as examples. The AI can study how those plugin actions are shaped, then return a full updated workflow JSON for you to paste back into WeWeb.

This only works well when you provide solid examples first. Without a few manually configured plugin-action workflows as references, the AI is guessing.

Steps

1. In WeWeb, manually build one or more workflows that already use the plugin actions you need (for example a Xano plugin action you configured yourself). Keep a few variations if you can. The more examples you give the AI, the better.
2. Open one of those workflows. In the top right of the workflow panel, open the ... menu next to the workflow name, then click Copy workflow.
3. Paste into your AI chat (ChatGPT, Claude, Cursor, and so on). You should see the workflow JSON.
4. Repeat for other example workflows if you have them, or keep them in the same chat as reference material.
5. Ask the AI to create or update a workflow based on those examples. Be specific about the change you want (for example which action to add, which fields to bind, or which conditions to set).
6. Ask the AI to return the full workflow JSON in the same format you pasted in. Do not ask it to summarize or partially rewrite the JSON.
7. Copy the JSON the AI returns.
8. In WeWeb, paste it as a new workflow. Open the result and check that the plugin actions, bindings, and flow look right.

What to expect

• The AI is not calling plugin tools through MCP here. You are doing a copy, edit, and paste loop with workflow JSON.
• Small mistakes in the JSON can produce a broken or incomplete workflow. Always open the pasted workflow in the editor and test it.
• This does not replace Integrations. When an Integration exists for your provider, use that instead so the AI can work through MCP tools normally.

CONTINUE LEARNING

Tool calls run against your real project, so a few habits go a long way once your agent is building.

Read the tips and guidelines →