shiply MCP in Windsurf

Connect shiply's MCP server to Windsurf to publish a site and manage its whole backend — database, functions, email, domains, analytics — from inside the agent.

Add the server

Edit ~/.codeium/windsurf/mcp_config.json. Windsurf uses serverUrl for remote HTTP servers:

{
  "mcpServers": {
    "shiply": {
      "serverUrl": "https://shiply.now/mcp"
    }
  }
}

To authenticate, add a Bearer shp_ key. If your Windsurf version supports headers on a remote server, add them alongside serverUrl:

{
  "mcpServers": {
    "shiply": {
      "serverUrl": "https://shiply.now/mcp",
      "headers": { "Authorization": "Bearer shp_YOUR_KEY" }
    }
  }
}

If your version rejects that shape, publish anonymously and claim the site afterwards, or check Windsurf's MCP docs for the current auth field. Get a key with shiply login (CLI), the dashboard, or the agent email-code flow.

Verify

Open the Cascade MCP panel and refresh, then ask the agent to call whoami (with a key) or publish_site (anonymous). An anonymous publish returns a claimUrl — open it to claim the site to an account.

What you get

• publish_site — ship any static or full-stack app to a live URL
• Database, server functions, and email tools for the app's backend
• Custom domains and auto-DNS tools
• Analytics and site management tools

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.