Back4app

com.back4appPublished by back4app.comOfficial publisherv1.0.0Updated Nov 5, 2026

Deploy anything that runs in a container and get a live HTTPS address. No account needed to start.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Back4app MCP server that lets an assistant deploy containerized apps and get a live HTTPS address, connecting over a remote OAuth-protected endpoint.

What you can do
  • Deploy container-based applications and obtain a live HTTPS address for them.
  • The server exposes no documented tool list, so the exact operations available to an assistant are not described in the supplied material.
  • It is reached as a hosted remote endpoint rather than a local package.
When to use it
Useful when you want an assistant to help ship something that runs in a container and get a reachable HTTPS address without setting up hosting by hand.
Requirements
A remote MCP client that supports streamable HTTP, connected to the hosted endpoint. OAuth authentication is required; no environment variables or headers are declared. An account is needed for authenticated use, though the description says no account is needed to start.
Before you install
Deployment creates and changes live infrastructure and publishes a publicly reachable HTTPS address, so review what gets deployed. Access is granted through OAuth, so check which account and permissions you authorize. The tool set is undocumented, so confirm capabilities before relying on it.

Installation

In SourceWeft

  1. Open Back4app 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.back4app%2Fback4app/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": {
    "back4app": {
      "type": "http",
      "url": "https://mcp.back4app.com/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.0LatestNov 5, 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.