Shiply MCP

Communauté Données et bases de données

Publish a static site or edge function to the web in one call, then manage updates, custom domains, SSL, env vars, databases and email.

Que pouvez-vous faire avec Shiply MCP ?

  • Publish & versions — publish_site (files → live *.shiply.now URL),
  • Status & verify — site_status, list_sites, verify_site (status + SSL +
  • Domains & SSL — add_domain, check_domain, set_handle (vanity subdomain)
  • Config — set_variable (encrypted per-user env), site access (password /
  • Site Data — read/write/export visitor records and collections
  • Databases — per-site SQL: Cloudflare D1 and Neon Postgres (provision, query,
  • Edge functions — deploy serverless functions alongside the static site
  • Email & inbox — send_email, list_site_inbox, set_mailbox, forward

Installation

Les étapes d'installation sont dans la documentation ci-dessous. Documentation

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. shiply — MCP server
  2. Connect
  3. Auth
  4. Tools
  5. Examples
  6. Pricing
  7. Links
  8. License

shiply — MCP server

shiply is the production backend for anything an agent builds — not just static hosting. An agent can publish any app in a single call — no account, no config — and then give it a real backend over the same MCP server: a SQL database, server functions, SSR, email (send and receive), custom domains, SSL, environment variables, site data, lead capture, and a marketplace to sell the site it built. Flat price, no usage meter.

The recommended way to use shiply is the hosted, remote MCP endpoint — connect to the live URL, nothing to run. This repo also ships a small local stdio MCP server (npx shiply-mcp / node index.mjs) that wraps shiply's public REST API directly (it is a real local server, not a proxy), for clients or hosts that prefer a local process. Listed on the Official MCP Registry as now.shiply/shiply.

Connect

Remote MCP endpoint (Streamable HTTP):

https://shiply.now/mcp

Add it to an MCP client (Claude Desktop, Cursor, Claude Code, etc.):

{
  "mcpServers": {
    "shiply": {
      "url": "https://shiply.now/mcp"
    }
  }
}
Local (stdio)

Prefer a local process? Run the bundled server — it calls shiply's public REST API directly (no proxy to the hosted endpoint):

{
  "mcpServers": {
    "shiply": {
      "command": "npx",
      "args": ["-y", "shiply-mcp"]
    }
  }
}

Or clone this repo and run npm install && node index.mjs. Set SHIPLY_API_KEY (shp_…) for owned-site operations; publish_site works without it. Local tools: publish_site, site_status, rollback_site, add_custom_domain, check_custom_domain.

Auth

Auth is optional. publish_site works anonymously — anonymous sites go live instantly and can be claimed into an account later. Pass a Bearer API key (Authorization: Bearer shp_…) to manage owned sites and unlock variables, custom domains, databases, and analytics. Mint a key from the email-code flow in llms.txt.

Tools

The live, authoritative tool list + JSON schemas are always at /.well-known/mcp.json. By area:

  • Publish & versions — publish_site (files → live *.shiply.now URL), update an existing site, rollback, delete_site
  • Status & verify — site_status, list_sites, verify_site (status + SSL + thumbnail in one call)
  • Domains & SSL — add_domain, check_domain, set_handle (vanity subdomain)
  • Config — set_variable (encrypted per-user env), site access (password / invite-only)
  • Site Data — read/write/export visitor records and collections
  • Databases — per-site SQL: Cloudflare D1 and Neon Postgres (provision, query, branch)
  • Edge functions — deploy serverless functions alongside the static site
  • Email & inbox — send_email, list_site_inbox, set_mailbox, forward
  • Contracts — create, send, and track e-sign contracts
  • Analytics — get_analytics (views, referrers)

Examples

Publish a folder, get a live URL (anonymous, no account):

// tool: publish_site
{ "files": [ { "path": "index.html", "content": "<h1>Hi</h1>" } ] }
// → { "url": "https://merry-maple-3kf2.shiply.now", "claimUrl": "..." }

Confirm it's live (status + SSL + screenshot) before reporting done:

// tool: verify_site
{ "slug": "merry-maple-3kf2" }
// → { "status": "LIVE", "ssl": { "valid": true }, "thumbnailUrl": "..." }

Pricing

Flat $0 / $8 / $24 — no usage meter, no surprise overage bill. See https://shiply.now/pricing.

License

MIT — see LICENSE. (This repo is a metadata-only descriptor; the shiply product source is not included.)

Questions fréquentes

Qu'est-ce que Shiply MCP ?

Publish a static site or edge function to the web in one call, then manage updates, custom domains, SSL, env vars, databases and email.

Comment installer Shiply MCP ?

Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.

Shiply MCP est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Shiply MCP ?

Il est publié par stevejford. AI.tn le référence sans le maintenir ni le recommander.

Issu des listes communautaires awesome-mcp-servers et du dépôt GitHub du projet. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.