# now.shiply/shiply

- Registry name: `now.shiply/shiply` · version 1.1.0
- Categories (automatic, keyword rules): Databases, Developer tools, Cloud & networking, Infrastructure & security, Docs & notes, Productivity
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=now.shiply%2Fshiply
- Server page: https://mcpstation.net/s/now.shiply--shiply.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://shiply.now/mcp`

## Tools (as reported by the server, not verified)

- `publish\_site`: Publish 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 version. Unchanged files are hash-skipped server-side, so re-publishing \(includi
- `site\_status`: Check any shiply slug or custom hostname: TLS certificate \(issuer, days left\) + HTTPS probe. ready=true means live.
- `verify\_site`: Edge-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 publishing to confirm the site is reachable.
- `list\_sites`: List the sites owned by this API key. Optional clientId filters to one client.
- `get\_site`: Site settings + version history for one of my sites.
- `delete\_site`: PERMANENTLY delete a site and all stored files. Irreversible — confirm with the user first.
- `rollback\_site`: Re-point a site to any finalized version \(rollback or roll-forward\). Get version ids from get\_site. Serving updates immediately.
- `list\_versions`: List 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\_site`: Download 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 built bundle \(\`.shiply/bundle/\*\`\), not original source.
- `set\_handle`: Give 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 shiply.now/@\<handle\>.\)
- `duplicate\_site`: Server-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\_site`: Copy 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 served bytes change.
- `set\_link`: Path-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 unmount.
- `set\_site\_access`: Protect 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 existing visitors.
- `get\_site\_access`: Read 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`: Return a JSON bundle of the user's profile, sites, Site Data, drives, and metadata \(secrets excluded\). Data portability.
- `whoami`: Who 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`: Get 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-clickable; show it in chat when a feature requires a higher plan. Returns plan id +
- `list\_drives`: List the user's private cloud Drives \(id, name\). Optional clientId filters to one client.
- `create\_drive`: Create a private cloud Drive \(plan-limited\). Pass client to file it under a client.
- `drive\_list\_files`: List files in a Drive \(driveId = drv\_…, or "default"\). Optional prefix filter.
- `drive\_put\_file`: Write a file into a Drive \(driveId = drv\_… or "default"\). content is utf8 or base64. Use for agent memory, notes, context, assets.
- `drive\_delete\_file`: Delete a file from a Drive.
- `publish\_from\_drive`: Snapshot a Drive \(or a prefix of it\) into a new live site at \<slug\>.shiply.now. Files copied server-side.
- `set\_profile`: Create 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\>.shiply.now, use set\_handle instead. enable shows the profile; autoAdd auto-lists
- `feature\_site`: Toggle whether an owned, public site appears in the public shiply Explore gallery \(https://shiply.now/explore\). Only public-access sites are eligible.
- `set\_variable`: Upsert 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 — attach it to a specific site with attach\_variable \(takes effect on that site'
- `list\_variables`: List the encrypted variables. Values are masked unless reveal=true.
- `delete\_variable`: Remove one variable by name.
- `attach\_variable`: Expose 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 function deploy.
- `detach\_variable`: Stop exposing a variable to a site's Worker env. Takes effect on the site's next function deploy.
- `list\_site\_variables`: Names of the variables attached to an owned site's Worker env \(values never shown here\).
- `list\_databases`: List 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 MCP server reached via GET /api/v1/databases/\{id\} \(see llms.txt\), which this id
- `create\_database`: Provision 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\_database`: PERMANENTLY delete a database and all its data. Irreversible — confirm with the user first.
- `attach\_database`: Bind 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`: List 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`: Page records from an owned site's collection, newest-first. limit ≤ 200 \(default 50\). cursor from a previous response's nextCursor.
- `data\_insert`: Insert 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`: Return 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\>\`.
- `add\_domain`: Serve a site on a domain the user owns. Returns the CNAME to add \(hostname → cname.shiply.now\); the certificate issues automatically once DNS resolves. Poll with check\_domain.
- `add\_custom\_domain`: Register a registrable domain \(e.g. example.com\) the user owns and detect its DNS provider. Returns the provider and whether one-click connect is available. Then attach sites with add\_subdomain.
- `add\_subdomain`: Serve an owned site at \<subdomain\>.\<domain\> \(use subdomain "@" or "" for the apex — apex needs a provider with CNAME flattening/ALIAS, e.g. Cloudflare\). Auto-registers the parent domain. Returns the CNAME record to add \(host -\> cname.shiply.now\); the certificate issues automatically once DNS resolve
- `set\_primary\_subdomain`: Mark a hostname as the primary \(canonical\) URL for its site. Sibling hostnames \(apex + www both pointed at the same site\) start 301-redirecting to it, preserving path + query. The host-side fix for the duplicate-content SEO problem. The first subdomain you add for a site is primary by default; call
- `list\_custom\_domains`: List registered custom domains grouped with their subdomains, each subdomain's site and status, and the detected provider.
- `connect\_provider`: Start one-click DNS connect for a registered custom domain. For Cloudflare-hosted domains this returns an authorize URL — SHOW THE USER the url as a clickable link; after they authorize, records are written automatically. For other providers, add the records manually.
- `sync\_dns`: For a connected custom domain, \(re\)write the CNAME records for all its subdomains automatically and report what changed. For unconnected domains, returns the records to add manually.
- `check\_custom\_domain`: Check whether a custom domain's subdomains are live: re-polls Cloudflare cert status + probes DNS/TLS/HTTPS on each subdomain. Poll this after connect\_provider / add\_subdomain to confirm the domain is serving. Returns per-subdomain status + tls + http + ready.
- `remove\_custom\_domain`: Remove a registered custom domain and all its subdomains; they stop serving immediately.
- `list\_domains`: List connected custom domains with status.
- `check\_domain`: Refresh certificate status + live TLS/HTTPS probe for a connected domain \(by id from list\_domains\).
- `remove\_domain`: Remove a connected domain \(by id\). It stops serving immediately.
- `get\_analytics`: Daily page views per site for the last 30 days.
- `create\_test`: Provision a demand test in one call: deploys a landing page with a native email-capture form and creates a confirmed-subscriber segment. Returns testId + live siteUrl. Share the siteUrl to collect signups; each signup gets a double-opt-in confirmation. Read progress with get\_test\_status.
- `list\_tests`: List your demand tests with signups + confirmed counts.
- `get\_test\_status`: ONE consolidated object: page funnel \(views, signups, confirmed, conversion\) ⊕ email events \(delivered/opened/clicked/bounced\) ⊕ a computed verdict. The single place to check progress — never query email separately.
- `send\_broadcast`: Send a campaign to this test's confirmed \(double-opt-in\) subscribers — the "we're live" email. An unsubscribe link is added automatically. Fails if there are no confirmed subscribers yet.
- `resend\_confirmation`: Re-send the double-opt-in confirmation to a signup that has not confirmed yet.
- `verify\_claim`: Confirm a pairing code shown in the user's browser at https://shiply.now/claim/\<slug\>?pair=1. Use ONLY in the agent session that originally published the site — it reads the claimToken from .shiply.json in the current working directory and proves to Shiply that this agent session is authorised to cl
- `list\_inbox`: List the user's email inbox threads \(outbound demand-test sends + inbound replies / unsubscribes / complaints / bounces\). Filter by tag.
- `read\_thread`: Return the thread metadata + all messages in chronological order. Use list\_inbox first to get a threadId.
- `summarize\_thread`: One-paragraph summary of the thread, oriented to the most actionable signal \(interest, complaint, question, unsubscribe\).
- `reply\_to\_thread`: Send an email reply on an existing thread. Goes FROM the original recipient address \(the \<slug\>@shiply.now alias the sender used\) and TO the original sender. Threaded via RFC 5322 In-Reply-To so Gmail/Outlook group it with the original. Subject defaults to 'Re: \<original\>' when omitted. Cap at 20,00
- `mark\_thread\_read`: Zero the unread counter for a thread. Useful after the agent has read but not acted. read\_thread already calls this implicitly; use this explicitly when you want to clear unread without re-fetching the thread body.
- `archive\_thread`: Soft-archive the thread \(sets archivedAt\). Hidden from the default inbox view; surface again with list\_inbox filter=archived. Reverse with unarchive\_thread.
- `unarchive\_thread`: Restore an archived thread \(clears archivedAt\). It reappears in the default inbox list. Pair with list\_inbox filter=archived to find archived threadIds first.
- `forward\_thread`: Forward a message from a thread \(default: the most recent message\) to a NEW recipient with an optional intro note. Body is composed as note + standard '---------- Forwarded message ----------' quote of the original. Goes from the thread's existing shiply alias so replies still route through the inbo
- `list\_test\_inbox\_addresses`: Return every active demand test's reply / inbound address \(\<slug\>@\<sitesDomain\>\). Use this when you need to TELL someone where to email — e.g. drafting a reply or sharing a test's contact address. Mail sent to these aliases lands in /dashboard/inbox tied to the test.
- `list\_unsubscribes`: Shortcut for list\_inbox with filter=unsubscribes — shows every thread tagged as an opt-out request.
- `list\_suppressions`: Return the user's suppression list — addresses \(and full domains\) that shiply skips when sending. Bounces, complaints, manual user adds, and AI-detected unsubscribes all land here.
- `add\_suppression`: Add an address \(or whole domain\) to the user's suppression list. Future confirmations and broadcasts will skip it across every test. Use kind='email' for a single address, kind='domain' for everyone @example.com.
- `remove\_suppression`: Delete one suppression by id. Use list\_suppressions first to find the id.
- `list\_complaints`: Return threads tagged as complaints \(spam reports\) OR bounces \(recipient rejected\). Read these before any further sending.
- `list\_projects`: List the dev's customer-intake projects \(newest first\). Optional filters: status \(draft\|intake\_open\|brief\_ready\|brief\_failed\|archived\), q \(case-insensitive match on label or customer email\), limit \(default 100\). Use to triage what's in flight before opening a specific project.
- `create\_project`: Spin up a new customer-intake project on the dev's account. Returns the project row plus intakeUrl — the public link the customer fills out \(10-step wizard\). If customerEmail is provided, shiply also emails them the intake invite. Use originatedFromSiteId to link a project to an existing site \(e.g.
- `get\_project`: Read one of the dev's projects by id — includes label, status, customer details, intake responses, AI brief, drive folder. Use before update\_brief / regenerate\_brief.
- `update\_brief`: Overwrite the project's working brief \(jsonb\). Hard-capped at 500 KB. Use to revise the AI-generated brief by hand; the original AI output is preserved separately in briefAiOriginal so you can always compare. Does not change status.
- `regenerate\_brief`: Re-run the MiniMax/Anthropic brief generator from the project's current intake\_responses and persist the result. Flips status to brief\_ready on success or brief\_failed on error. Use after the customer edits answers post-submit, or when the first AI attempt failed.
- `archive\_project`: Move a project to status='archived'. Hidden from the default dashboard list. Optional reason is shown on the project page. Restore later with restore\_project.
- `restore\_project`: Move an archived project back to status='draft' so it reappears in the active list. Idempotent on non-archived projects? No — server rejects the transition unless the project is currently archived.
- `list\_project\_files`: Return the customer-uploaded files for one project \(path, size, contentType, createdAt\). Empty when no drive folder exists yet \(no uploads\). Use to inspect what intake assets the customer attached.
- `resend\_intake\_invite`: Re-fire the 'your developer sent you a project intake' email to the project's customer. Throws invalid\_request if the project has no customerEmail \(the dev needs to set one via the dashboard first — customer email isn't agent-patchable\). Use when the customer says they didn't receive the link.
- `list\_listings`: Return every marketplace listing the seller owns \(any status: draft, live, paused, sold\). Includes site slug and current price. Use to see what's for sale across the account.
- `create\_listing`: Publish \(or upsert\) a marketplace listing for an owned site. Requires Stripe Connect set up \(status='ready' — see get\_connect\_status\). priceCents = whole-dollar between 100 and 999900. termsMode='standard' uses shiply's template; 'custom' requires termsCustom ≥50 chars. jurisdiction is required \(e.g
- `update\_listing`: Patch a listing by siteSlug — change price, pitch, terms, jurisdiction, or status \(draft\|live\|paused\). Sold listings cannot be edited. Status transitions enforced server-side. Use to pause sales or drop the price.
- `delete\_listing`: Take a listing off the public marketplace by moving it to status='draft'. Marketplace v1 keeps the row so analytics + future re-listing work — there's no hard delete. Sold listings can't be modified. Use to stop accepting offers without losing pricing history.
- `list\_my\_sales`: Return every marketplace order for sites the user sold \(incl. pending, paid, refunded, failed, disputed\). Most recent first. Use to surface revenue + which orders are still inside the 30-day refund window \(refundExpiresAt \> now\).
- `list\_my\_orders`: Return every marketplace order the user PURCHASED. Most recent first. Shows the acquired site, paid amount, and whether the order is still inside the 30-day refund window. Use to recap what the user owns by purchase.
- `refund\_order`: Issue a full refund on a paid order the user sold. Must be inside the 30-day refund window \(server enforces\). Triggers a Stripe refund; the webhook flips the order to 'refunded' and reverts site ownership to the seller. Idempotent on already-refunded orders.
- `get\_connect\_status`: Return the seller's Stripe Connect state: not\_started \| in\_progress \| pending\_verification \| ready \| disabled. When status \!= 'ready' the user can't list sites. Includes a one-shot onboardingUrl \(if not\_started or in\_progress\) and dashboardUrl \(if ready\). Refreshes from Stripe on every call.
- `list\_sending\_domains`: Return every BYO sending domain the user has added \(id, domain, fromAddress, status: pending\|verified\|failed, DNS records\). Use to inspect verification state or find the id of a domain to verify/remove.
- `add\_sending\_domain`: Register a domain the user owns for outbound demand-test sends. Returns DNS records \(SPF, DKIM, MX\) to add at the DNS provider. After DNS propagates, call verify\_sending\_domain. Cannot be a shiply.now subdomain.
- `verify\_sending\_domain`: Trigger Resend to re-check the domain's DNS records, persist the new status. Call after adding the DNS records returned by add\_sending\_domain. Status flips to 'verified' once SPF + DKIM + MX all check out.
- `remove\_sending\_domain`: Delete a BYO sending domain. Any demand tests bound to it fall back to the managed shiply sender. Also GCs the underlying Resend domain. Irreversible — re-adding requires re-verifying DNS.
- `contract\_draft`: Draft a contract from a brief\_ready project. Auto-fills 8 fields from the AI brief, Stripe Connect default currency, and dev profile. Returns the contract row with status='draft' so the dev can review fields before sending. After this, edit fields via PATCH /api/v1/contracts/\{id\} \(no MCP edit tool y
- `contract\_send`: Send a draft contract to the customer. Validates all 8 fields are non-empty, computes content\_hash, flips project to contract\_sent, fires the customer email. Same handler works for amendment drafts — sending an amendment does not move project state.
- `contract\_amend`: Create an amendment to a SIGNED parent contract. Scope delta required; fee delta and target date optional. Returns the draft amendment for editing before send — call contract\_send with the returned amendment id to fire it. Cannot amend an amendment \(amend the parent instead\).
- `contract\_pdf`: Get the signed contract PDF as a base64-encoded download. PDF includes the contract, signature certificate, and any signed amendments. Returns \{ filename, contentType, base64 \}. Errors with conflict:contract\_not\_signed if the parent contract has not been signed yet.
- `contract\_status`: Read the current state of a contract: status, sent\_at, viewed\_at, signed\_at, signer info, content\_hash, plus any amendments. Use this to check whether a customer has signed yet. Returns \{ contract, amendments \} — the contract row matches GET /api/v1/contracts/\{id\}.
- `deploy\_function`: Deploy a Worker function to a site. The function runs on every request to \<slug\>.shiply.now and can receive webhooks, run on cron triggers, and access bindings \(D1, secrets, env vars\). Requires Developer plan. Use when the user wants webhook receivers, cron jobs, or a backend for their site.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html