Skip to main content
Glama
claude-host
by Elitespec

@elitespec/claude-host

Deploy Claude-generated websites to EliteSpec hosting in one tool call. An MCP (Model Context Protocol) server for Claude Code and Claude Desktop.

Install

npm install -g @elitespec/claude-host
elitespec-host install   # prints Claude config JSON to paste
elitespec-host login     # one-time auth

Related MCP server: Just Publish MCP Server

What it does

Once installed in Claude, the model can call:

  • deploy_site(name, files, industry?) — ship a static site to <slug>.elitespec.co.nz

  • update_site(siteId, files) — push changes to an already-deployed site

  • list_sites() — list the user's hosted sites

Example conversation:

User: Make me a landing page for my Auckland bakery.

Claude: (writes HTML, CSS, JS in the conversation)

User: Publish it.

Claude: (calls deploy_site with the files)

Live at: https://auckland-bakery-a1b2c3.elitespec.co.nz

Pricing

  • Free tier: <slug>.elitespec.co.nz subdomain, up to 3 sites.

  • $9/mo: custom domain, unlimited sites, no EliteSpec branding.

  • $29/mo: everything above plus Forge AI upgrades (rewrite copy, add pages, stock photos matched to your industry).

Docs

Full docs at https://forge.elitespec.co.nz/docs/claude-host

Security

Your Claude Code session never sees your password. Login is handled by the CLI and stores a token at ~/.elitespec/host.json.

License

MIT

Available Tools

3 tools
deploy_siteA

Deploy a static website to EliteSpec hosting. Returns a live URL on *.elitespec.co.nz. Use this when the user has a website (HTML + CSS + JS + images) ready to go live. Works best for landing pages, small business sites, and portfolios. First deploy requires a one-time EliteSpec account (free tier available).

Inputs: name (required), files (required), industry.

list_sitesA

List the authenticated user's hosted sites on EliteSpec.

Inputs: no named parameters.

update_siteA

Push updated files to an existing EliteSpec-hosted site. Only files in the payload are overwritten; other files remain.

Inputs: siteId (required), files (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: deploying a new site, listing existing sites, and updating a site. There is no ambiguity or overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: deploy_site, list_sites, update_site. The naming is uniform and predictable.

    Tool Count4/5

    With 3 tools, the server covers the core lifecycle for static site hosting (deploy, list, update), which is appropriate for the domain. A delete operation is missing but does not severely impact the count.

    Completeness3/5

    The tool surface covers deploy, list, and update, but lacks a delete operation for removing hosted sites. This is a notable gap for a hosting service, as agents may need to clean up old sites.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI tools to deploy static websites to Dorelli Hosting and check their status via MCP, using deploy_site and site_status tools.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      sitectrl turns a plain-language description into a real, hosted, live website — not a mockup. Your AI can ask sitectrl's builder to do it (create_site), or write the code itself and push the files (write_site_files + publish_site). Every site ships with hosting, SSL, working contact forms, and private built-in analytics; domains and email connect in-product.
      MIT