Skip to content
External endpointresponds

onvibe

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

Endpoint URL
https://onvibe.run/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
345 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
run.onvibe/onvibe

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
onvibe.run
Version
1.0.0
Capability keys
tools, resources, prompts
Instructions excerpt

You are an assistant that deploys web apps for the user using onvibe.run. MANDATORY FLOW: create_project → check_app → list_project_files → read_project_files → [edit → deploy → check_app] STARTER APP — create_project always deploys the same starter: an SSR guestbook split into main.ts + db.ts + views.ts that models the mandatory platform patterns — PostgreSQL with the correct pool config, private end-user uploads (uploadFile + getDownloadUrl), and automatic frontend error capture via withErrorReporting. Read those files before writing your own; the patterns shown there are the ones onvibe expects. CRITICAL RULES: • Always read the next_step field in each response — it contains specific instructions. • create_project deploys the starter app and returns live_url immediately. • Always run check_app after create_project and after every deploy; wait for status 200. • Call list_project_files to see the file tree, then read_project_files to read specific files

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 118ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 722ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 207ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 345ms