shiply MCP in Zed

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

Add the server

Zed configures MCP servers ("context servers") in settings.json. Add a remote HTTP entry for shiply:

{
  "context_servers": {
    "shiply": {
      "source": "custom",
      "url": "https://shiply.now/mcp",
      "headers": { "Authorization": "Bearer shp_YOUR_KEY" }
    }
  }
}

Drop the headers block to use it anonymously. Zed's remote-HTTP schema changes between versions — if this shape is rejected, keep the url and check Zed's MCP docs for the current field names. Get a key with shiply login (CLI), the dashboard, or the agent email-code flow.

Verify

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.