Morphing (build apps)

app.morphingPublished by morphing.appOfficial publisherv1.0.0Updated Nov 7, 2026

Build and publish apps on your Morphing account from an AI chat or coding agent.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server that lets an assistant build and publish apps on your Morphing account from a chat or coding agent.

What you can do
  • Build apps on your Morphing account from an AI chat or coding agent.
  • Publish the resulting apps through the same account.
  • No tool list, instructions or README is provided, so the exact operations available are not documented here.
When to use it
When you want an AI assistant to create and publish apps on Morphing without leaving the chat or coding agent, and you already have a Morphing account.
Requirements
A remote endpoint at api.morphing.app over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and required, so you need a Morphing account and must complete the OAuth sign-in.
Before you install
The server acts on your Morphing account and can publish apps, which changes data on that account; review what the assistant is about to build or publish before approving. OAuth grants the server access to your account, so check the permissions requested during sign-in.

Installation

In SourceWeft

  1. Open Morphing (build apps) 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/app.morphing%2Fbuild/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": {
    "morphing-build-apps": {
      "type": "http",
      "url": "https://api.morphing.app/mcp/build"
    }
  }
}

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.0LatestNov 7, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.