Connect via MCP

shiply runs a remote MCP server at https://shiply.now/mcp (Streamable HTTP). Connected agents get 40 tools: publish_site, site_status, list_sites, get_site, delete_site, set_handle, variables, custom domains, analytics, whoami, and auto-DNS domain tools (add_custom_domain, add_subdomain, list_custom_domains, connect_provider, check_custom_domain, remove_custom_domain, sync_dns, verify_claim).

No setup required to publish: publish_site works without authentication — it creates an anonymous site (24-hour lifetime) and returns a one-time claimToken/claimUrl. Add an API key and every publish is permanent, plus the management tools unlock.

Claude Code

claude mcp add --transport http shiply https://shiply.now/mcp \
  --header "Authorization: Bearer shp_YOUR_KEY"

(Drop the --header to use it anonymously.)

Cursor / Windsurf / generic JSON config

{
  "mcpServers": {
    "shiply": {
      "url": "https://shiply.now/mcp",
      "headers": { "Authorization": "Bearer shp_YOUR_KEY" }
    }
  }
}

Codex CLI

[mcp_servers.shiply]
url = "https://shiply.now/mcp"
http_headers = { "Authorization" = "Bearer shp_YOUR_KEY" }

Getting a key

shiply login (CLI), the dashboard, or the agent email-code flow: POST /api/auth/agent/request-code {"email"} → POST /api/auth/agent/verify-code {"email","code"} → { apiKey }.

Tips for agents

• publish_site takes files inline (utf8 or base64) up to 50 files / 2 MB total — enough for almost any generated site. Bigger: use the REST flow.
• site_status returns the SSL certificate + readiness for any slug or custom hostname — poll it after add_domain until ready: true.
• Anonymous publishes: save the claimToken — it is shown exactly once.
• verify_claim({ code: "SHIPLY-XXXXXXXX" }) lets the agent confirm a pairing code shown in the user's browser at /claim/<slug>?pair=1, binding the anonymous site to their account without requiring them to paste any token.