Aurora

build.auroraPublished by aurora.buildOfficial publisherv0.1.0Updated Oct 24, 2026

Create, edit, preview, and deploy full-stack web apps to a live URL from any MCP client.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Aurora lets an assistant create, edit, preview and deploy full-stack web apps to a live URL, connecting from any MCP client over a remote endpoint.

What you can do
  • Build and edit full-stack web apps from the assistant's side
  • Preview an app before publishing it
  • Deploy an app to a live URL
  • No tool list is published, so exact operations are not documented; the description covers creating, editing, previewing and deploying web apps.
When to use it
Useful when you want an assistant to scaffold or change a web application and get a shareable live URL without setting up your own build and hosting pipeline.
Requirements
A remote MCP endpoint at mcp.aurora.build using streamable HTTP. OAuth authentication is required, so an Aurora account and a client that supports OAuth are needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your Aurora account. Deploying publishes apps to a live public URL, and edits change existing projects, so review what the assistant creates or deploys before sharing it.

Installation

In SourceWeft

  1. Open Aurora 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/build.aurora%2Faurora/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": {
    "aurora": {
      "type": "http",
      "url": "https://mcp.aurora.build/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

1
  1. v0.1.0LatestSep 16, 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.

Other Aurora integrations