Backendless Console SDK MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with programmatic access to Backendless administration and developer APIs.

Backendless MCP enables AI assistants to directly manage your Backendless applications through natural language:

Create a new table called "Products" with columns: name (string), price (number), and inStock (boolean)

List all users who registered in the last 7 days

Your AI assistant can now:

• 1️⃣ Manage databases, users, files, etc.
• 2️⃣ Query data and perform operations
• 3️⃣ All without leaving your development environment

🚀 What is this for?

This MCP server enables AI assistants (like Claude, ChatGPT, Cursor, etc.) to interact with your Backendless applications through the Backendless Console SDK. It exposes a comprehensive set of tools for managing databases, users, API services, cloud code, and other Backendless resources directly from your AI-powered development environment.

Key benefits:

• Direct Backendless integration: Access all Backendless admin APIs through natural language
• Dynamic tool loading: Tools are automatically generated from the Backendless Console SDK
• Secure authentication: Supports OAuth2 authentication
• Flexible usage: Use hosted endpoints

✨ Features

• Comprehensive API coverage: Automatically exposes all available Backendless Console SDK methods as MCP tools
• Session management: Maintains authenticated sessions with Backendless servers
• OAuth2 authentication method:
• Multi-cluster support: Connect to US, EU, local, or Backendless PRO clusters
• Hosted: Use Backendless-provided MCP endpoints (zero setup)

📋 Prerequisites

• Backendless account with API access

📦 Installation

Note: Installation is not required if you're using the Backendless hosted MCP endpoints.

🛠️ Usage

Backendless Hosted MCP (Easiest - Recommended)

Each Backendless cluster provides a hosted MCP server endpoint. This is the easiest way to get started - no installation or server setup required!

Available endpoints:

• US Cluster: https://develop.backendless.com/mcp
• EU Cluster: https://eu-develop.backendless.com/mcp

Install in Cursor

Go to: Settings → Cursor Settings → MCP → Add new global MCP server

Cursor Hosted Connection

{
  "mcp": {
    "servers": {
      "backendless": {
        "type": "http",
        "url": "https://develop.backendless.com/mcp"
      }
    }
  }
}

Cursor Local Connection

Install in Claude Code

Claude Code Hosted Connection

Run this command:

claude mcp add --transport http backendless https://develop.backendless.com/mcp

Install in VS Code

Add to your VS Code MCP settings. See VS Code MCP docs for more info.

VS Code Hosted Connection

{
  "mcp": {
    "servers": {
      "backendless": {
        "type": "http",
        "url": "https://develop.backendless.com/mcp"
      }
    }
  }
}

Install in Windsurf

Add to your Windsurf MCP configuration. See Windsurf MCP docs for more info.

Windsurf Hosted Connection

{
  "mcpServers": {
    "backendless": {
      "serverUrl": "https://develop.backendless.com/mcp"
    }
  }
}

Install in Cline

You can easily install Backendless through the Cline MCP Server configuration:

1. Open Cline
2. Click the hamburger menu icon (☰) to enter the MCP Servers section
3. Choose Remote Servers tab
4. Click the Edit Configuration button
5. Add backendless to mcpServers:

Cline Hosted Connection

{
  "mcpServers": {
    "backendless": {
      "url": "https://develop.backendless.com/mcp",
      "type": "streamableHttp"
    }
  }
}

Install in Roo Code

Add this to your Roo Code MCP configuration file. See Roo Code MCP docs for more info.

Roo Code Hosted Connection

{
  "mcpServers": {
    "backendless": {
      "type": "streamable-http",
      "url": "https://develop.backendless.com/mcp"
    }
  }
}

Install in Claude Desktop

Hosted Connection

Open Claude Desktop and navigate to Settings > Connectors > Add Custom Connector. Enter the name as Backendless and the remote MCP server URL as https://develop.backendless.com/mcp.

Install in Opencode

Add this to your Opencode configuration file. See Opencode MCP docs for more info.

Opencode Hosted Connection

{
  "mcp": {
    "backendless": {
      "type": "remote",
      "url": "https://develop.backendless.com/mcp",
      "enabled": true
    }
  }
}

Install in Qodo Gen

See Qodo Gen docs for more details.

1. Open Qodo Gen chat panel in VSCode or IntelliJ
2. Click Connect more tools
3. Click + Add new MCP
4. Add the following configuration:

Qodo Gen Hosted Connection

{
  "mcpServers": {
    "backendless": {
      "url": "https://develop.backendless.com/mcp"
    }
  }
}

Install in Trae

Use the Add manually feature and fill in the JSON configuration information for that MCP server. For more details, visit the Trae documentation.

Trae Hosted Connection

{
  "mcpServers": {
    "backendless": {
      "url": "https://develop.backendless.com/mcp"
    }
  }
}

Testing with MCP Inspector

Start your server and test with the MCP Inspector:

# Start the server
BACKENDLESS_HOST=us PORT=3003 npm run start:http

# In another terminal, run the inspector
npx @modelcontextprotocol/inspector

Configure the inspector:

• Transport Type: Streamable HTTP
• URL: http://localhost:3003/mcp

🔨 Available Tools

Tools are dynamically loaded from the Backendless Console SDK definitions. The available tools include operations for:

• Data Management: Create, read, update, delete tables and records
• User Management: User registration, authentication, role management
• API Services: Manage and invoke custom API services
• Cloud Code: Deploy and manage server-side business logic
• Files: File upload, download, and management
• Messaging: Push notifications and email management
• Geolocation: Location-based services
• And more: All Backendless Console SDK capabilities

Special Tools

• getSDKInfo: Get current SDK session information and status

🔐 Authentication

For Hosted & Self-Hosted HTTP Mode

The server supports OAuth2 authentication method:

OAuth2 Bearer Token: Use standard OAuth2 Bearer authentication

Authorization: Bearer YOUR_TOKEN

When authentication fails, the server responds with a 401 status and WWW-Authenticate header pointing to the OAuth2 discovery endpoints.

🏗️ Architecture

┌─────────────────┐
│  AI Assistant   │
│ (Claude, etc.)  │
└────────┬────────┘
         │ MCP Protocol
         │ (HTTP)
         ▼
┌─────────────────┐
│   MCP Server    │
│  (This Package) │
└────────┬────────┘
         │ Backendless Console SDK
         ▼
┌─────────────────┐
│   Backendless   │
│     Cluster     │
└─────────────────┘

🚨 Troubleshooting

Connection Issues

Symptom: Cannot connect to Backendless cluster

Solutions:

• Check your network connection and firewall settings
• For hosted endpoints, ensure you can access https://develop.backendless.com or https://eu-develop.backendless.com in your browser

Tool Not Found Errors

Symptom: "Tool not found" errors when trying to use specific operations

Solutions:

• Use getSDKInfo to check available methods
• Ensure you're using the latest version of the MCP server
• Check the Backendless Console SDK version being used

Port Already in Use

Symptom: "EADDRINUSE" error when starting HTTP server

Solutions:

• Change the PORT environment variable to an available port
• Check if another process is using port 3003: lsof -i :3003 (Unix/Mac) or netstat -ano | findstr :3003 (Windows)
• Kill the process using the port or choose a different port

🔗 Links

• Backendless Documentation
• Model Context Protocol
• Backendless Console SDK NPM
• Backendless Console SDK GitHub

📄 License

MIT

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

💬 Support

For issues related to:

• This MCP server or Backendless platform: Backendless Support
• MCP protocol: MCP Documentation