hyphertext · model context protocol
mcp-connected app builder

Your AI assistant,
wired straight into your sites.

Hyphertext runs a full MCP server — the same protocol Claude and other AI assistants use to call tools directly. Connect once, and your assistant can create pages, edit files, save real data, and publish — all without leaving your conversation.

how to connect
01

Sign in to Hyphertext

Create a free account — your first published site is free forever, no card required.

02

Add the connector

In your AI client, add a custom MCP connector pointed at https://www.hyphertext.com/mcp, then approve access — it's the same OAuth sign-in you already trust.

03

Just ask

Tell it to import your HTML, build something from scratch, or edit a page you already have. It's live in seconds.

what your assistant can do
✎

Pages

Create, edit, publish, and delete pages — plus find-and-replace edits for small changes without resending the whole document.

create_pageupdate_page_htmlstr_replace_page_htmlpublish_pageget_pagelist_pages
▤

Multi-file projects

index.html stays the entrypoint; add sibling .js/.css/.json files a project can reference with a plain relative path.

create_project_fileupdate_project_filestr_replace_project_filelist_project_files
⬡

Persistent database

A real, server-side JSON record store per project — the assistant seeds it at build time; the live page reads and writes it at runtime.

db_insertdb_querydb_updatedb_delete
⚿

Secrets

The assistant can declare which env vars a project needs — the actual value is only ever entered by you, directly, in Studio.

declare_project_secretlist_project_secretsdelete_project_secret
⌘

Files & assets

Images, PDFs, and docs upload in small chunks over the same MCP connection — no separate network access required.

start_asset_uploadupload_asset_chunkfinish_asset_uploadlist_assets
how access is scoped

Your assistant can only ever touch your own account.

No standing service-role access

Every tool call runs with your own Supabase session token, scoped by the same row-level security policies as the web app — never a privileged service key.

Secret values never pass through chat

An assistant can declare that a project needs an API key, but the actual value is only ever typed in by you, directly, in Studio — never in the conversation.

OAuth, not a shared password

You approve access once through a standard OAuth consent screen. Revoking it at any time removes the connection immediately.

Scoped to your pages only

Every tool call is checked against page ownership server-side — there's no way for a connected assistant to see or touch another account's sites.

ready when you are

Connect your assistant in under a minute.

Free to start. No card required.

Connect via MCP →