Skip to content
Start building

Agent integrations

Your app in any assistant

Publish your Vibely web app with its own MCP server. Your users add one link to their assistant and ask it to search, book or update things in your app.

Start buildingRead the docs
Web apps · every plan

Agent integrations turn a published Vibely web app into an MCP server. Vibely writes the server at /mcp and proposes one tool for each action the app already does, so your users can search, create or update things in your app from ChatGPT, Claude or Cursor.

One link puts your app in the assistant

CRM

Tools: find_customer, update_deal_stage. Your users ask: “Which deals haven’t moved in two weeks?”

Questions your users can ask

  • Your users ask

    “Which deals haven’t moved in two weeks?”

  • Your users ask

    “Submit this request and tell me what’s still waiting on me”

  • Your users ask

    “Summarize this week’s signups”

  • Your users ask

    “Book me the first free slot on Thursday afternoon”

How it works

  1. Choose who can connect

    People signed in to your app, or anyone. Protected mode uses your app’s own sign-in, so each person reaches only their own data.

  2. Vibely writes the server

    An MCP server at /mcp inside your live app, one file per tool, built from what your app already does. It uses your app’s connected Supabase project.

  3. Review the tools

    Each tool is marked Read-only or Can modify data. Ask in chat to add, remove or change one. Edits wait until you publish.

  4. Publish and share the link

    Your users add the link to their assistant as a custom connector, and sign in if you require it.

Stay in control

  • Runs in your real app

    It isn’t a copy. The server runs inside your published app with your app’s own logic, and your pages don’t change.

  • Public or signed-in

    Protected mode uses your app’s own sign-in, so each person reaches only their data. Public tools can be called by anyone; treat what they return as public.

  • You decide when it goes live

    Tool changes wait for your next publish, and unpublishing the app takes the MCP server offline straight away.
    How publishing works

  • Web apps only

    Agent integrations are available for web apps. Mobile projects show a note instead of the panel.
    Building web apps

Good fits

Apps that hold data people want to reach from where they already work.

  • CRM

    Find a customer, check a deal, move it along.

  • Client portal

    Clients file requests and check status from their assistant.

  • Booking

    Open slots and bookings, one sentence away.

  • Dashboard

    Ask for this week’s numbers instead of opening a tab.

Frequently asked questions

The Vibely MCP server lets your own assistant build and publish Vibely apps. Agent integrations work for your users: they put the app you built inside their assistant, so they can search, book or update things in it.

Enabling it, and every change you ask for afterwards, is a normal build turn and uses credits like any other build. Tool calls from your users don’t use Vibely credits; they run your app’s own logic against your Supabase project.

No. Agent integrations are available for web apps. Mobile projects show “Agent integrations are available for web apps.”

A web app with a connected Supabase project, published on Vibely. The MCP link only works on the published app.

Yes. Click Remove agent integrations at the bottom of the panel, or ask in chat, then publish. Unpublishing the app also takes the MCP server offline immediately.

Yes. Once it is published, add it to Vibely as a connector and mention it in any Vibely chat to pull live data or run its tools.

Your app in assistants

Start buildingRead the docs