MCP clients
Connect shiply's MCP server to any agent and publish the app and its backend from one connection
shiply's MCP isn't just static publishing. The same connection exposes the database, server functions, email, custom domains, and analytics tools — so an agent can publish the app and its backend from one MCP connection. Other agent-native hosts only push static files over MCP; shiply gives the agent the whole backend.
shiply runs a remote MCP server at https://shiply.now/mcp (Streamable HTTP).
A legacy SSE endpoint lives at https://shiply.now/sse. Connected agents get
100+ tools: publish_site, site_status, list_sites, get_site,
delete_site, set_handle, variables, custom domains, analytics, whoami,
and auto-DNS domain tools.
publish_site works without authentication — it creates an anonymous site
(24-hour lifetime) and returns a one-time claimToken/claimUrl. Add a
Bearer shp_ API key and every publish is permanent, plus the management tools
unlock.
Get a key with shiply login (CLI), the dashboard, or
the agent email-code flow.
Per-client setup
The cardinal rule for agents
NEVER create a new site to update an existing one. Always re-publish to the SAME slug.
See also Connect via MCP and the quick start.