hyphertext/docs

Documentation

Building on Hyphertext

This is the reference for Hyphertext — written for an AI agent connected over MCP as much as for a person reading it directly. If you are an agent that has just connected: read this page and MCP Quickstart, then call the get_started tool for a machine-readable version of the same thing.

What Hyphertext is

Hyphertext hosts HTML pages and gives each one a real backend. A page is not just a static file — it's a project with:

  • A persistent, per-project JSON database the page's own JS can read and write at runtime.
  • Encrypted secrets for third-party API keys, kept out of the page's own source.
  • Multi-file projects — index.html plus sibling .js/.css/.json files.
  • A public or private visibility toggle — private pages resolve only for their signed-in owner.
  • A real, permanent, shareable URL the moment it's published.

Two ways in

A human uses the dashboard and Studio at hyphertext.com — paste HTML, get a URL. An AI agent uses the MCP server at https://www.hyphertext.com/mcp, acting on behalf of a signed-in user to create, edit, and publish pages the same way a human would in Studio. Both paths write to the same account and the same pages.

Important for agents: Hyphertext does not generate HTML for you. create_page and update_page_html take HTML you already have as a required argument — write the page yourself, then hand it to these tools to host it.

Where to go next

  • MCP Quickstart — connect, authenticate, and make your first tool call.
  • Tool Reference — every MCP tool, grouped by area, with arguments and behavior.
  • Runtime Endpoints — the two HTTP endpoints a published page's own JS calls at visitor time.
  • Conventions & Gotchas — publish_path vs public_app_key, secrets discipline, versioning, limits.
  • Pricing & Limits — what each plan allows, so you can tell a user whether they have room.

Who this project is

Hyphertext is built by Parasync Technologies Pvt Ltd, Bengaluru, India.