Model Context Protocol (MCP)

21 min

The Model Context Protocol (MCP) is a standard for connecting Large Language Models (LLMs) to platforms like Back4App. This guide covers how to connect Back4App to the following AI tools using MCP:

Cursor
Windsurf (Codium)
Visual Studio Code (Copilot)
Cline (VS Code extension)
Claude desktop
Claude code

Once connected, your AI assistants can interact with and query your Back4App projects on your behalf.

AI agents with MCP are configured to have full access to your Back4App apps, which includes the ability to create, modify, and delete resources. We strongly recommend first trying on a test account and app to understand its capabilities and potential impact before using it with production environments.

Prerequisites

An account created at back4app.com. (each new account has a deafult limit of apps if you need more please contact us);
A recent NodeJs version installed (16^);
For better results we recommend to use the most advanced LLM Models and coding Agents;
Activate Web-Hosting for visualizing deployments on your subdomain;

1 - Create a Account Key

First, go to your Back4App dashboard and create a personal access token:

Log into your Back4App account
Hover over the "Hello, [username]" menu
Go to Account Keys and create a new key
Give it a name that describes its purpose, like "AI Assistant MCP"
Copy the token securely - you won't be able to see it again

Then give your account key token a name and click on +.

This token will be used to authenticate the MCP server with your Back4app account.

2 - Install MCP - Auto

Follow these steps to install Back4app MCP on your prefered IDE/LLM:

2.1- Run Installation Command

Run this command on your terminal substituting <ide> for your prefered enviroment and YOUR_ACCOUNT_KEY for your account key copied on Step 1.

npx @back4app/mcp-installer install <ide> --account-key YOUR_ACCOUNT_KEY

The specific commands for each IDE are listed below:

Cursor

npx @back4app/mcp-installer install cursor --account-key YOUR_ACCOUNT_KEY

Windsurf

npx @back4app/mcp-installer install windsurf --account-key YOUR_ACCOUNT_KEY

Visual Studio

npx @back4app/mcp-installer install vscode --account-key YOUR_ACCOUNT_KEY

Cline

npx @back4app/mcp-installer install cline --account-key YOUR_ACCOUNT_KEY

2.2- Verify Connection

Cursor : Go to Settings -> Cursor Settings -> MCP

Windsurf: Find the toolbar above the Cascade input and click on refresh

Visual Studio: Click on configure tools on the Agent Mode (Copilot) and find the back4app MCP tools.

3 - Configure in your AI tool - Manual

MCP compatible tools can connect to Back4App using the Back4App MCP server. Below are instructions for connecting to this server using popular AI tools:

Open Cursor and go to Cursor menu.
Navitage to Cursor->Settings->Cursor Settings->MCP
Click on +Add a new global MCP

Then add the following configuration:

macOS / Linux

{
  "mcpServers": {
    "back4app": {
      "command": "npx",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Windows

{
  "mcpServers": {
    "back4app": {
      "command": "npx.cmd",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Replace <account-key> with your account key copied from back4app.
Save the configuration file

Alternative Setup

If you prefer a project setup you can create a local project config file:

Create a .cursor directory in your project root if it doesn't exist
Create a .cursor/mcp.json file if it doesn't exist and open it
Add the connfiguration mentioned before

Open Windsurf and navigate to the Cascade assistant
Tap on the hammer (MCP) icon, then Configure to open the configuration file
Add the following configuration:

macOS / Linux

{
  "mcpServers": {
    "back4app": {
      "command": "npx",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Windows

{
  "mcpServers": {
    "back4app": {
      "command": "npx.cmd",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Replace <account-key> with your account key copied from back4app.
Save the configuration file and reload by tapping Refresh in the Cascade assistant
You should see a green active status after the server is successfully connected

Open VS Code and create a .vscode directory in your project root if it doesn't exist
Create a .vscode/mcp.json file if it doesn't exist and open it
Add the following configuration:

macOS / Linux

{
  "inputs": [
    {
      "type": "promptString",
      "id": "back4app-account-key",
      "description": "Back4App personal access token",
      "password": true
    }
  ],
  "servers": {
    "back4app": {
      "command": "npx",
      "args": ["-y", "@back4app/mcp-server-back4app@latest"],
      "env": {
        "BACK4APP_ACCOUNT_KEY": "${input:back4app-account-key}"
      }
    }
  }
}

Windows

{
  "inputs": [
    {
      "type": "promptString",
      "id": "back4app-account-key",
      "description": "Back4App personal access token",
      "password": true
    }
  ],
  "servers": {
    "back4app": {
      "command": "npx.cmd",
      "args": ["-y", "@back4app/mcp-server-back4app@latest"],
      "env": {
        "BACK4APP_ACCOUNT_KEY": "${input:back4app-account-key}"
      }
    }
  }
}

Save the configuration file
Open Copilot chat and switch to "Agent" mode. You should see a tool icon that you can tap to confirm the MCP tools are available
Once you begin using the server, you will be prompted to enter your personal access token. Enter the token that you created earlier

For more info on using MCP in VS Code, see the Copilot documentation.

Open the Cline extension in VS Code and tap the MCP Servers icon
Tap Configure MCP Servers to open the configuration file
Add the following configuration:

macOS / Linux

{
  "mcpServers": {
    "back4app": {
      "command": "npx",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Windows

{
  "mcpServers": {
    "back4app": {
      "command": "npx.cmd",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Replace <account-key> with your account key copied from back4app.
Save the configuration file. Cline should automatically reload the configuration
You should see a green active status after the server is successfully connected

Open Claude desktop and navigate to Settings
Under the Developer tab, tap Edit Config to open the configuration file
Add the following configuration:

macOS / Linux

{
  "mcpServers": {
    "back4app": {
      "command": "npx",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Windows

{
  "mcpServers": {
    "back4app": {
      "command": "npx.cmd",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Replace <account-key> with your account key copied from back4app.
Save the configuration file and restart Claude desktop
From the new chat screen, you should see a hammer (MCP) icon appear with the new MCP server available

Outdated Node.js installations can cause the npx command to fail in Claude Desktop. We recommend uninstalling any versions older than 16 and using Node.js v16 or higher.

Create a .mcp.json file in your project root if it doesn't exist
Add the following configuration:

macOS / Linux

{
  "mcpServers": {
    "back4app": {
      "command": "npx",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Windows

{
  "mcpServers": {
    "back4app": {
      "command": "npx.cmd",
      "args": [
        "-y",
        "@back4app/mcp-server-back4app@latest",
        "--account-key",
        "<account-key>"
      ]
    }
  }
}

Replace <account-key> with your account key copied from back4app.
Save the configuration file
Restart Claude code to apply the new configuration

Outdated Node.js installations can cause the npx command to fail in Claude Code. We recommend uninstalling any versions older than 16 and using Node.js v16 or higher.

3 - Available Tools

Once connected, your AI assistant can perform a wide range of tasks on your Back4App account. Here are some of the available tools:

App Management

create_parse_app - Create a new Parse app
get_parse_apps - Get a list of all your Parse apps
get_parse_app - Get details for a specific Parse app
set_current_app - Set a default app for subsequent operations
get_current_app - Get the currently set default app

Direct API Access (Parse REST API)

call_parse_api - Calls the Parse Server REST API endpoints to fully manage your app.

Database Operations – Create, read, update, delete objects in any class – Rich querying (filters, sorting, pagination, count, aggregate, distinct)

User Management & Security – Sign up / log in / log out / password reset – Roles, ACLs & CLPs to lock down data at object- and class-level

Real-Time & Push – LiveQuery over WebSockets (subscribe to creates/updates/deletes) – Push notifications & installation records

Call Cloud Code functions – Cloud Functions and Scheduled Jobs – Before/after triggers, custom webhooks

Files, Analytics & Extensions – File upload/download

Cloud Code and Web Hosting on Parse App

list_cloud_code_and_web_hosting_files - List all cloud code and web hosting files
get_file_content - View the content of specific files
deploy_cloud_code_files - Deploy cloud code files to your app
deploy_web_hosting_files - Deploy web hosting files to your app

4 - Security Considerations

The MCP server has full access to your Back4App account with the permissions of your personal access token. This means AI tools can create, modify, and overwrite your apps and data. Always take the following precautions:

Use a dedicated test account for initial experimentation
Create a separate access token specifically for MCP use
Never share your configuration files containing access tokens
Review all code and API Calls generated or modified by AI before deploying to production
Revoke access tokens immediately if you suspect any unauthorized use

5 - Troubleshooting

Common Issues

Connection failures: Ensure your personal access token is valid and correctly entered
Server not responding: Check that you have Node.js installed and that npx is working correctly
Permission errors: Verify that your access token has the necessary permissions
Updates not appearing: Some MCP clients require a restart after configuration changes

6 - Next Steps

Your AI tool is now connected to Back4App using MCP. Try asking your AI assistant to create a new app, deploy some cloud code, or manage your data using natural language.

If you experience any issues or have feedback, please send us a message at: [email protected]

Conclusion

With Back4App's MCP integration, you can leverage the power of AI Agents to accelerate your development workflow. From creating and configuring apps to deploying code and managing data, your AI assistant can now seamlessly interact with the Back4App platform on your behalf.

Model Context Protocol (MCP)

Prerequisites

1 - Create a Account Key

2 - Install MCP - Auto

2.1- Run Installation Command

2.2- Verify Connection

3 - Configure in your AI tool - Manual

Cursor

Windsurf

Visual Studio(Copilot)

Cline

Claude desktop

Claude Code

3 - Available Tools

App Management

Direct API Access (Parse REST API)

Cloud Code and Web Hosting on Parse App

4 - Security Considerations

5 - Troubleshooting

Common Issues

6 - Next Steps

Conclusion