Onvibe

run.onvibePublished by onvibe.runOfficial publisherv0.1.0Updated Oct 24, 2026

Talk to Claude and get a live web app deployed to a real URL, with Postgres, storage and cron.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant turn a conversation into a live web app deployed at a real URL, with Postgres, storage and cron.

What you can do
  • Build and deploy a web app from a conversation, publishing it to a real URL.
  • Provision backing services for the app, including Postgres and file storage.
  • Set up scheduled jobs (cron) for the deployed app.
  • No tool list is published, so the exact operations available are not documented.
When to use it
Useful when you want an assistant to go from an idea or discussion straight to a running, publicly reachable web app with a database and scheduled tasks, without setting up hosting yourself.
Requirements
A remote MCP endpoint at the provider's host, reached over streamable HTTP. No authentication, environment variables or headers are declared, and no local package is needed.
Before you install
The server deploys apps to public URLs and provisions databases, storage and scheduled jobs, so it creates and changes live resources. No authentication is declared, so check how access to the endpoint and to deployed apps is controlled before connecting.

Installation

In SourceWeft

  1. Open Onvibe in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/run.onvibe%2Fonvibe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "onvibe": {
      "type": "http",
      "url": "https://onvibe.run/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.