Your first app on Haechy
Add Haechy to Claude as a custom connector with the address https://mcp.haechy.com/mcp (ChatGPT,
Codex, VS Code and Cursor work with the same address). The sign-in
window that opens is where you create your account, with an email link and a code sent to your phone. Then ask
Claude to put your app online: it creates the app, deploys it and tells you where it lives.
Not sure what to build? Start from a ready-made app: ask Claude for the expense claims, leave requests, bookings, approvals or weekly check-in starter and it is online in a minute or two. See the five starter apps
Pick the way you use Claude
- claude.ai in the browserOpen Customize > Connectors, choose "+ Add" then "Add custom connector", and paste the address.
- Claude DesktopUses the connectors on your Claude account, so one setup covers it.
- Claude CodeOne command:
claude mcp add --transport http haechy https://mcp.haechy.com/mcp.
Using another assistant? Follow the guide for ChatGPT, Codex, VS Code with GitHub Copilot or Cursor. The rest of this page works the same way there; only the assistant's name changes.
Whichever you use, the name can be "Haechy" and sign-in is by OAuth, so there is no key or secret to copy.
What to say first
Describe the app you want online, or point Claude at the one you already have. Claude starts with get_started, which reports your account, plan and usage against the limits, then calls create_app, deploy_app and get_deploy. If your phone check isn't finished, get_started gives Claude a link to console.haechy.com/onboarding/phone to pass on to you.
- You
Put my team's stock-count app online with Haechy.
- Tool
get_startedDoneAccount active, Free plan. Apps 0/2. Next: create an app, then deploy it.
- Tool
create_appstock-countDoneCreated at stock-count.haechy.app. Access: private.
- Tool
deploy_appDoneDeploy started. Check progress with get_deploy in about 20 seconds.
- Tool
get_deployIn progressBuilding. Check again in about 20 seconds.
- Tool
get_deployDoneLive.
- Claude
It's live at stock-count.haechy.app. Only you can open it for now.
Once your first app is online, see what else it can do: schedules, file uploads, your own address and more.
An app's name can be up to 80 characters. Its address uses a slug of 3 to 30 lowercase letters, digits and hyphens. If you don't pick a region, the app goes in your account's default region, which is suggested from your phone number's country. Every new app starts private.
Signing up in the sign-in window
When you connect, Claude opens Haechy's console to sign in. New to Haechy? Choose Create a free account and enter your email and a password (your password manager can save it). We also email you a link to confirm your address, but you don't have to wait for it. Then Haechy texts a code to your mobile number, and your account becomes active once you enter it. Last comes a page saying Claude "wants to manage your Haechy apps"; choose Allow to finish connecting.
Haechy is available in the US, Canada, the UK, the EU and EEA, Switzerland, Australia and New Zealand. We're starting with the places where we can support billing, tax and local rules properly. Sign-up asks for a mobile number from one of these countries; we use it to keep spam and abuse off Haechy.
The number has to come from one of those countries. Internet (VoIP) numbers and numbers whose type can't be identified are refused, and a number that is already on another account can't be used again. Known disposable email domains are refused too. Haechy allows up to three codes per hour for one account or number.
What the deploy check can stop
Before building, on every plan, Haechy scans the uploaded code for keys and passwords written into it, .env files, packages with known vulnerabilities or malware, and risky code. A key or password in a file, or a .env file in the upload, always stops the deploy (files named example, sample or template are fine). A malicious package, a critical vulnerability in a package the app runs with, or request input passed straight to code, a shell, SQL or a template stops it too. Anything else is a warning. get_deploy tells Claude the file and line, or the package and the version to move to, for each finding. Claude fixes it and deploys again, so you rarely need to act. If a flagged package or line is a finding you accept, the workspace owner or an admin can allow that exact finding from a link in the console; Claude can't.
Deploy progress runs through pending, uploaded, building, scanning, starting and live. A deploy marked blocked or failed comes back with the reason.
Who can open the app?
A new app is private: you and anyone you list can open it, at your-slug.haechy.app. To let colleagues in, ask Claude to add them by email, or (on paid plans) to open the app to everyone at your company's email domain. They sign in with an emailed link and don't need a Haechy account. Sharing and sign-in has the details.
When the app needs an outside service
An app can't reach anything on the internet until you approve it. If the code mentions a payment provider, a calendar or an AI service, Claude asks Haechy for access to that host and gives you a link with the reason. Open it in the console and approve or deny. Approving outside services shows what that page looks like.