Embarko

io.github.swayammaheshwariPublished by GitHub account swayammaheshwariv1.0.0Updated Oct 26, 2026

Deploy and host AI-built apps and websites, and get a live URL without any DevOps setup.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Embarko is a remote MCP server that lets an assistant deploy and host AI-built apps and websites, returning a live URL without DevOps setup.

What you can do
  • Deploy AI-built apps and websites to hosting
  • Get a live URL for a deployed site without DevOps setup
  • No tool list is published, so the exact operations an assistant can call are not documented in the supplied material.
When to use it
Use it when you have an app or website generated with AI help and want the assistant to publish it and hand back a working link, rather than setting up hosting and deployment yourself.
Requirements
A remote MCP endpoint at mcp.embarko.ai over streamable HTTP; OAuth sign-in is required. No environment variables, headers or local packages are declared.
Before you install
OAuth grants the server access to your Embarko account, so review the scopes requested at sign-in. Deployment publishes content publicly at a live URL; check what is being made public before deploying. No tool list is published, so confirm what actions it can take before connecting.

Installation

In SourceWeft

  1. Open Embarko 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/io.github.swayammaheshwari%2Fembarko-mcp/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": {
    "embarko": {
      "type": "http",
      "url": "https://mcp.embarko.ai/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. v1.0.0LatestOct 26, 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.