Agents Index

Shiply

Online

Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price.

Visit publisherConnectJSON

What it can do: 80 tools

  • publish_sitePublish files to the web → live URL at <slug>.shiply.now. UPDATING: never create a new site for changes — re-call with claimToken (anonymous sites) or slug (sites you own with a Bearer key) and the SAME URL gets the new
  • site_status read-onlyCheck any shiply slug or custom hostname: TLS certificate (issuer, days left) + HTTPS probe. ready=true means live.
  • verify_site read-onlyEdge-check a shiply slug or custom hostname and return a structured readiness report: status (LIVE/PENDING), SSL details (valid, issuer, daysLeft), HTTP probe, and a presigned thumbnail URL when available. Use this after
  • list_sites read-onlyList the sites owned by this API key. Optional clientId filters to one client.
  • get_site read-onlySite settings + version history for one of my sites.
  • delete_sitePERMANENTLY delete a site and all stored files. Irreversible — confirm with the user first.
  • rollback_siteRe-point a site to any finalized version (rollback or roll-forward). Get version ids from get_site. Serving updates immediately.
  • list_versionsList a site's finalized deploys newest-first (id, createdAt, isLive, fileCount, bytes), capped at 20. Pair with rollback_site: pick a version id from here and re-point the site to it.
  • pull_siteDownload the current files of a site you own (or created via a platform connection) so you can edit and republish to the same slug with publish_site. Static sites return editable source; framework/SSR sites return the bu
  • set_handleGive ONE site a vanity URL: rename it to <handle>.shiply.now (3-30 chars, a-z 0-9 -). The old address 301-redirects for 30 days. (For a portfolio page listing all your sites, use set_profile instead — that lives at shipl
  • duplicate_siteServer-side copy of an owned site under a new slug — instantly live. Copies files + title; does NOT copy access settings, domains, or data. Great for iterating on variants.
  • promote_siteCopy the EXACT live bytes of one owned site (srcSlug — your preview) into another owned site (destSlug — your production site / custom domain), no rebuild. Dest keeps its slug, domains, and access settings; only the serv
  • set_linkPath-mounting: serve an owned target site at a path on an owned host site (host/docs -> target). location is a path like "docs", or "__root__" for the host root. Both sites must be owned by you. Pass remove=true to unmou
  • set_site_accessProtect an owned site (paid plans). mode 'public' (anyone), 'password' (supply password), or 'restricted' (supply allowedEmails and/or allowedDomains — only those can request a login code). Changing any setting signs out
  • get_site_access read-onlyRead an owned site's current access policy (mode: public/password/restricted, allowedEmails, allowedDomains, hasPassword). Read-only counterpart to set_site_access — check before changing it.
  • export_account read-onlyReturn a JSON bundle of the user's profile, sites, Site Data, drives, and metadata (secrets excluded). Data portability.
  • whoami read-onlyWho am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.
  • get_account_status read-onlyGet the signed-in account's plan, capabilities, and upgrade URL. Call this FIRST when figuring out what features you have access to — it tells you exactly what's available and what's blocked. The upgrade_url is human-cli
  • list_drives read-onlyList the user's private cloud Drives (id, name). Optional clientId filters to one client.
  • create_driveCreate a private cloud Drive (plan-limited). Pass client to file it under a client.
  • drive_list_files read-onlyList files in a Drive (driveId = drv_…, or "default"). Optional prefix filter.
  • drive_put_fileWrite a file into a Drive (driveId = drv_… or "default"). content is utf8 or base64. Use for agent memory, notes, context, assets.
  • drive_delete_fileDelete a file from a Drive.
  • publish_from_driveSnapshot a Drive (or a prefix of it) into a new live site at <slug>.shiply.now. Files copied server-side.
  • set_profileCreate or update the user's public PORTFOLIO page at shiply.now/@<handle> (handle 3-30 chars a-z0-9-) — a landing page listing the user's sites. This is NOT a site's address: to give one site a vanity URL like <handle>.s
  • feature_siteToggle whether an owned, public site appears in the public shiply Explore gallery (https://shiply.now/explore). Only public-access sites are eligible.
  • set_variableUpsert a key/value in the user's encrypted variable store (UPPER_SNAKE name, ≤8 KiB value). Use for API keys the user's sites/agents need, e.g. SUPABASE_URL. NOTE: saving alone does NOT expose it to any site Worker's env
  • list_variables read-onlyList the encrypted variables. Values are masked unless reveal=true.
  • delete_variableRemove one variable by name.
  • attach_variableExpose one saved variable to ONE owned site's Worker env (plain_text binding). Opt-in per site — unattached variables are never injected, because the Worker runs the site's own code. Takes effect on the site's next funct
  • detach_variableStop exposing a variable to a site's Worker env. Takes effect on the site's next function deploy.
  • list_site_variables read-onlyNames of the variables attached to an owned site's Worker env (values never shown here).
  • list_databases read-onlyList the SQL databases (D1 or Neon Postgres) on my account, including which owned site (if any) each is attached to. Call this BEFORE db_query/db_schema-style work to discover a databaseId — those live on a per-database
  • create_databaseProvision a SQL database — D1 (default, free) or Neon Postgres (--postgres, developer plan). Optionally attach it to an owned site's Worker env in the same call (siteSlug); otherwise attach it later with attach_database.
  • delete_databasePERMANENTLY delete a database and all its data. Irreversible — confirm with the user first.
  • attach_databaseBind an existing database to one owned site's Worker env (the binding name chosen at create_database time). Takes effect on the site's next function/publish deploy.
  • data_list_collections read-onlyList collections declared in an owned site's .shiply/data.json with current record counts. Empty list means the site has no manifest yet — scaffold one with `shiply data init`.
  • data_query read-onlyPage records from an owned site's collection, newest-first. limit ≤ 200 (default 50). cursor from a previous response's nextCursor.
  • data_insertInsert one record into a collection. Goes through the same public visitor endpoint a browser would use — manifest access.insert decides whether it is allowed. Use to seed waitlist data, test forms end-to-end, etc.
  • data_export_collection read-onlyReturn up to `limit` records (default 1000, max 5000) from a collection — for snapshotting into agent context. For larger sets use the CLI: `shiply data export <slug> <collection>`.

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http shiply https://shiply.now/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://shiply.now/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "shiply": {
      "url": "https://shiply.now/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "shiply": {
      "type": "http",
      "url": "https://shiply.now/mcp"
    }
  }
}

Questions

What does Shiply do?

Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price. It exposes 80 tools to AI assistants.

What tools does Shiply provide?

80 tools, including publish_site, site_status, verify_site, list_sites, get_site, delete_site, rollback_site, list_versions, pull_site, set_handle, duplicate_site, promote_site….

How do I connect Shiply to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://shiply.now/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Shiply require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Shiply online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Shiply?

shiply.now. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Databases & Data