Add Hedy as an MCP server. AI builds the whole application.
One connection to Claude, ChatGPT, Cursor, or Claude Code is all it takes. From there your AI assistant configures the Hedy project, writes the scope, plans the work, builds the application, publishes it to a live URL, and keeps operating it — without you stitching together a task tracker, a code editor, and a hosting account.
mcp.hedyassist.com/mcp with OAuth or a connector token.
The MCP connection is the product. Everything else follows from it.
Configuration, planning, implementation, publishing, and ongoing operations all run through the same connection against the same project. Nothing is re-explained to a blank prompt or copied into a separate hosting account.
Connect
Hedy MCP ServerAdd one remote MCP server to Claude, ChatGPT, Cursor, or Claude Code. Your assistant gains 40+ grouped tools plus live project resources. How it works →
Configure & Plan
Project, Scope, Task BoardYour assistant creates the project, writes real scope documents, and generates a prioritized task board with due dates and tags — the backlog it then works through.
Build & Publish
Application PlatformApp files, server-side functions, routes, customer sign-in, and isolated data — tested against real requests, then promoted to a live URL or your own domain.
Operate & Iterate
Logs, Schedules, RevisionsExecution logs, product analytics, scheduled jobs, push, and realtime are all readable over the same connection. Every deploy is a revision you can roll back.
Supporting surfaces
The Chrome extension captures real-world context — screenshots, session recordings, and QA findings anchored to a live page — so your assistant builds against evidence instead of a description. The Hedy Workspace gives your team a human view of the same project: boards, scope, assets, discussions, and activity history.
From an empty project to a live application, in one conversation.
Once Hedy is connected, your assistant is not limited to advice. Each step below is a real tool call it makes against your project.
Add the Hedy MCP server
Point your assistant at https://mcp.hedyassist.com/mcp and authorize with OAuth or a connector token. Nothing to install, nothing to run locally.
Set up the project and its scope
Your assistant creates the project in the right workspace and turns your requirements into real scope documents, so later work can be checked against them instead of against memory.
Generate the task board
Work items get priority, board status, due dates, and tags. Hedy becomes the backlog for the build, and your assistant keeps it current as it implements each item.
Author the application
App files for the front end, server-side JavaScript for the API, shared modules for reused logic, behavior routes for redirects and auth gates, plus project-isolated data, customer sign-in, and write-only secrets.
Test, then go live
Your assistant runs real requests against the draft app and reads the responses and logs, then promotes it to project--workspace.apps.hedyassist.com or a custom domain you own.
Diagnose and iterate
Execution logs, errors, and product analytics come back through the same connection, so a bug found in production gets fixed in the same conversation — and every deploy is a revision you can roll back.
See the full twelve-step lifecycle and the tools behind it →
Hedy hosts the application it helps you build.
This is what your assistant produces over MCP: not a repository you still have to deploy, but a running application with real accounts, real storage, and a real address. You can inspect and adjust any of it from the Hedy Workspace.
Hosted Web Apps & Custom Domains
Every app receives an instant single-label address (project--workspace.apps.hedyassist.com). Attach custom domains with automatic certificate provisioning.
Isolated Application Data
Applications store and retrieve structured data via ctx.data. Each project's data is strictly isolated per company and project.
Customer Accounts & Themed Login
Manage end-user authentication for your app consumers, with themed login pages, OAuth, remember-me sessions, and protected routes.
Server-Side App AI
Call AI models directly inside server-side functions with ctx.askai. Summarize documents, power assistants, and run classification workflows.
Integrations & Outbound Fetch
Securely connect to approved external services through catalog-driven integration recipes (including Stripe, HubSpot, and selected Front workflows) or declared HTTPS hosts. Front recipes support application or per-connection-rule webhook setup; sending customer messages through Front is blocked.
Push & Realtime Channels
Send Web Push notifications and publish low-latency WebSocket updates for collaborative dashboards and live UI invalidation.
Scheduled Automation
Execute server functions headlessly on recurring cron cadences or one-shot times for reports, reminders, and cleanup routines.
Revisions & Rollback
Maintain structured source manifests with file checksums, revision history, deployment logs, and one-click rollback.
One remote server. Nothing to install.
Hedy is a remote MCP server, so connecting it is a one-time setup step in your assistant — not a local process to run or a package to maintain. Access is always scoped to the companies and projects your Hedy account already has.
Claude and ChatGPT: connect with OAuth as a custom connector or custom app — no credential ever enters a prompt.
Cursor, Claude Code, and automation: connect with a connector bearer token issued from the Hedy Workspace.
40+ grouped tools: a deliberately compact surface, so your assistant keeps context available for the actual work.
Guided from the start: Hedy ships its own build guide, project resources, and prompts, so your assistant knows the workflow before it begins.
Connect Cursor or Claude Code in seconds
Add Hedy to your MCP settings with a connector token from the Hedy Workspace:
{
"mcpServers": {
"hedy": {
"url": "https://mcp.hedyassist.com/mcp",
"headers": {
"Authorization": "Bearer ct_company.ut_user"
}
}
}
}Claude custom connectors and ChatGPT custom apps use OAuth instead of a token. Sign in to Hedy for the exact setup steps for your assistant, and treat connector tokens like credentials.
Most AI coding setups stop at the code. Hedy carries the whole lifecycle.
An assistant that can only write files leaves you to run the project, wire up hosting, and re-explain context every session. Hedy gives it a project to configure, a backlog to work, and somewhere to actually publish.
- Requirements live in meeting notes and chat history
- Tasks hand-copied into a separate tracker
- Every AI session starts from a blank prompt
- Generated code still needs a hosting account, a database, and auth wired by hand
- Production errors sit in a log tool the assistant cannot read
- ✓ Configure: Project and scope documents created in place
- ✓ Plan: A real task board your assistant works through
- ✓ Build: Files, server functions, routes, data, and customer auth
- ✓ Publish: A live URL and your own domain, no separate host
- ✓ Operate: Logs and analytics your assistant reads and fixes against
Built for people who want the application, not just the plan.
Founders & Small Businesses
Describe the application you need to Claude or Cursor and let Hedy configure the project, build it, and host it. No hosting account, database, or auth provider to set up yourself.
Start with the MCP →Consultants & Analysts
Capture how a customer actually works, turn it into a scoped backlog, and ship the intake forms, dashboards, and internal tools that come out of it.
Digital Agencies
Collect client feedback on live sites, check requests against the signed scope, convert findings into tasks, and publish custom client portals on your own domain.
Explore Agency Workflows →Product & QA Teams
Give your assistant the same page-anchored evidence your team works from, so fixes are built against screenshots and recordings instead of a summary.
Explore Website QA →An AI assistant with real write access needs real boundaries.
Letting an assistant build and publish software is only safe if the platform constrains it. Hedy enforces strict data boundaries, resource limits, and an audit trail rather than unrestricted execution.
An MCP connection can only reach the companies and projects your Hedy account already has, at the role you already hold.
Server functions run in per-request sandboxes with enforced memory, CPU, and execution time caps, and no ambient network or filesystem access.
Application data is scoped per company and project at the storage layer, so one app cannot reach another project's records.
Application and company secrets are write-only, and a function only ever receives the secrets it explicitly declares.
Project administrators set allowed AI models, request size limits, and daily usage allowances for AI calls.
Every change records the authenticated person behind it, and every deployment is a revision you can roll back.
Common questions about Hedy
What is Hedy?
Hedy is an MCP-driven application creation system. You add Hedy as an MCP server in Claude, ChatGPT, Cursor, or Claude Code, and from that single connection your AI assistant can configure a project, write its scope, plan the work, build the application, publish it to a live URL, and keep operating it.
What can my AI assistant do once Hedy is connected over MCP?
Everything from project setup through live operations. It creates the project, writes scope documents, generates a prioritized task board, uploads app files, writes server-side functions and shared modules, defines routes, configures customer sign-in and data storage, runs test requests, promotes the app live, attaches a custom domain, and then reads execution logs and analytics to diagnose and fix issues.
Which AI tools can connect to Hedy?
Claude custom connectors and ChatGPT custom apps connect to the remote MCP endpoint at https://mcp.hedyassist.com/mcp using OAuth. Cursor, Claude Code, and local automation connect using a Hedy connector bearer token. There is nothing to install locally. See the full setup guide.
What kind of applications can be built and hosted on Hedy?
You can build marketing pages, customer portals, intake forms, internal dashboards, AI-powered tools, integrated business applications, realtime collaborative tools, and scheduled automated workflows—complete with user auth, isolated database storage, and custom domains.
Do I need the Chrome extension to use Hedy?
No. The MCP connection and the application platform work on their own. The Chrome extension is a supporting capture surface: it lets you review a live site or prototype and attach screenshots, recordings, and QA findings to the project so your AI assistant builds against real-world evidence instead of a description.
Is Hedy free during early access?
Yes. Hedy is free during early access—including MCP AI connections, workspace access, Chrome extension usage, and hosted application publishing.
Add Hedy as an MCP server and build the whole thing.
Sign in to get your MCP connection details and the setup steps for Claude, ChatGPT, Cursor, or Claude Code.