Back4app

npx add-mcp 'https://mcp.back4app.com/mcp'

Connect your AI tools to Back4app using the Model Context Protocol (MCP), an open standard that lets AI assistants work with your Back4app applications.

The Back4app MCP server deploys anything that runs in a container, from web apps and websites to APIs and backends, and gives it a live HTTPS address. It follows builds, reads logs, deploys new versions, sets environment variables and rolls back.

Server

• URL: https://mcp.back4app.com/mcp

• Transport: Streamable HTTP

• Authentication: none to start. With no account connected, the server makes a temporary account when you ask to deploy. To use your Back4app account, sign in with OAuth 2.1.

Connect

npx plugins add back4app/back4app-plugin

The plugin installs the MCP server and the Web Deployment skill. See Back4app Plugin.

Open this link to add Back4app as a connector, then connect it.

Add a remote MCP server with the URL https://mcp.back4app.com/mcp and the Streamable HTTP transport. For example:

{
  "mcpServers": {
    "back4app": {
      "type": "http",
      "url": "https://mcp.back4app.com/mcp"
    }
  }
}

The name of the field for the transport changes between clients (type: "http", streamableHttp, httpUrl, serverUrl): use the one your client documents.

Accounts and sign-in

Connection	What happens
No account connected	When you ask to deploy, the server makes a temporary account: 24 hours, one application, Free plan, built with a buildpack. You keep the application by opening the claim link and signing in.
Signed in	The agent works with your Back4app account and its applications. Ask it to sign in to Back4app; your client opens the browser to approve.

Each connection is listed in your Back4app account under Connected Agents, where you can end it.

Safety

Changes to a live application are shown to you as a summary first and run only after you agree.

• update_app and rollback change a live application in two steps: the first call answers a summary and changes nothing. The agent shows you the summary and goes on only if you agree. A confirmation lasts 5 minutes and works once.

• Environment variable values are never read back by any tool.

• Logs are what your application wrote. The server marks them as data, never as instructions for the agent.

• A deployment blocked by a security check is reported to you; it is not retried.

Back4app Backend

This server covers Web Deployment (Containers). For the Back4app Backend (Parse database, Cloud Code, Web Hosting), use the, which runs locally with an account key. It will join this server later. If you use both, give the local one a different name, such as back4app-backend, so it doesn't replace this one in your client's configuration.

Tools

See Back4app MCP tools.