Handsome Hosting

npx add-mcp 'https://hosting.handsome.co.il/mcp'

Connect to Handsome Hosting

For when the person asks you to connect them to Handsome Hosting (hosting.handsome.co.il). Show them each step as you go; nothing on this page asks you to act without their go-ahead.

Handsome Hosting deploys and manages the person's websites and apps through an MCP server. Once connected, the person asks you in their own words and you deploy, check status, read logs, connect domains and more through the tools; money steps end on an approval page mailed to the person.

Claude Code

Run this in the person's shell, from their project folder:

claude mcp add --transport http handsome https://hosting.handsome.co.il/mcp

To make it available in every project instead, add the scope flag between the name and the address: claude mcp add --transport http --scope user handsome https://hosting.handsome.co.il/mcp.

A running session does not load a new server by itself. Tell the person to restart Claude Code (claude --continue brings this conversation back), then type /mcp, pick handsome and choose the authenticate option. A browser window opens on Handsome Hosting: they sign in or create an account and approve once. Where no browser can open, Claude Code prints the URL to open by hand. Newer Claude Code versions can also run the login from the shell with claude mcp login handsome.

Cursor

Merge this handsome entry into the mcpServers object of .cursor/mcp.json in the project, or of ~/.cursor/mcp.json for every project. Keep the person's other servers; never replace the whole file with this snippet.

{ "mcpServers": { "handsome": { "url": "https://hosting.handsome.co.il/mcp" } } }

The MCP section of Cursor Settings then shows the server waiting for login; the person clicks it and approves in the browser that opens.

What the connection is

• The approval in the browser is the person's consent and replaces keys. Never ask them for a key, a token or a password. If they made a key by hand on their account page, they paste it themselves.
• Keys created either way are listed and revoked on https://hosting.handsome.co.il/account?tab=builders.
• Reads cost 1 point and writes 5 from a daily budget per key; a budget-paused answer names the reset time.
• Before the first upload, call the preflight tool and run its checks on the person's machine; create_project and deploy require its report and refuse without a pass.
• Anything that costs money or cannot be undone returns an approval link mailed to the person; tell them to check their mail, then poll action_status.
• A partner account (our partner program, https://hosting.handsome.co.il/policy/partners) can also have a client pay for a new site: the preflight needs list then asks who pays, and create_project with payer client mails the client a signup and payment link instead of an approval; follow it with action_status and the inviteId.
• A partner account with servers for client sites (kind host in list_services) can put a new site on one for the site fee alone: create_project or create_wordpress with hostId; hostId new buys a server of its own.
• Form messages go to the account address unless the person picks others: ask them, send the choice as formSendTo in the pre-flight report, and set_form_recipients (or the site page) changes it later.
• WordPress: list_services marks it; create_wordpress orders one (no upload, no preflight); then wp_login, wp_migration, wp_status, wp_plugin, wp_theme, wp_upload_extension and list_backups; content goes through its REST API with wp_app_password; deploy does not apply.
• On a static site the platform adds an accessibility panel. Do not build one.

Terms for builders: https://hosting.handsome.co.il/policy/builders. The page for people: https://hosting.handsome.co.il/connect.