Ember Websites

com.embersitesPublished by embersites.comv0.14.1Updated Oct 24, 2026

Describe your business. Get a beautiful website, built and published for you from Claude or ChatGPT.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant turn a description of a business into a built and published website.

What you can do
Ember Websites is a remote MCP endpoint that connects an assistant to a website-building service. According to the registry description, you describe your business and the service produces a beautiful website that is built and published for you, from Claude or ChatGPT. No individual tools are listed in the manifest.
When to use it
Useful when you want a finished, published website generated from a short business description without building it yourself, and you are already working inside a supported assistant such as Claude or ChatGPT.
Requirements
A remote streamable HTTP endpoint at embersites.app; no local package or runtime is needed. OAuth authentication is required, so you need an account with the provider and must complete the OAuth sign-in flow.
Before you install
The server publishes a website on your behalf, so content may go live publicly without a separate review step. It requires OAuth sign-in to a third-party service, and the business description you provide is sent to that provider.

Installation

In SourceWeft

  1. Open Ember Websites in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.embersites%2Fember/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ember-websites": {
      "type": "http",
      "url": "https://embersites.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.14.1LatestOct 12, 2026
  2. v0.14.0Oct 10, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.