developer-toolsapi_key

Backendless

Backendless is a comprehensive backend-as-a-service (BaaS) platform providing scalable backend functionality for mobile and web applications, including user authentication, data persistence, file storage, and custom API services.

Verdict

Backendless is a backend-as-a-service platform that handles user auth, file storage, databases, and scheduled tasks. This MCP exposes 31 tools that let your team manage Backendless resources directly from Switchy — change user passwords, copy files between directories, create and delete timers for recurring jobs, provision new Hive key-value stores, and organize file hierarchies. Developers and ops teams get the most value: you can script routine backend tasks in plain English instead of switching to the Backendless console. You'll need an API key with appropriate scopes; the MCP can't provision new apps or modify billing settings.

Common use cases

Reset user passwords from support chat
Schedule nightly data export timers
Organize uploaded files into dated folders
Provision Hive stores for new features
Audit and delete obsolete scheduled tasks

Integration

Vendor: Backendless
Category: developer-tools
Auth: API_KEY
Tools: 31
Composio slug: backendless

Tools

Change User Password
Tool to change the password for the current user. use when you need to securely update a user's password after login. example prompt: "change my password to n3wp@ssw0rd!".
Copy File
Tool to copy a file or directory within backendless file storage. use when duplicating files to a new location after verifying source and destination paths.
Create Backendless Hive
Tool to create a new hive. use when you need to provision a new hive resource before performing hive operations. example: create a hive named 'grocerystore'.
Create Backendless Timer
Tool to create a new timer with schedule and code. use when scheduling recurring or one-off tasks to run server-side logic after confirming parameters.
Create Directory
Tool to create a new directory at the specified path. use when you need to organize files under a new folder structure.
Delete Backendless Timer
destructive
Tool to delete a backendless timer by name. use when you need to remove a scheduled timer after confirming its name.
Delete Directory
destructive
Tool to delete a directory at the specified path in backendless file storage. use when you need to remove folders after confirming the path.
Delete File
destructive
Tool to delete a file at the specified path in backendless file storage. use after confirming the file's relative path and filename.
Delete User
destructive
Tool to delete a user by user id. use when removing a user account after confirming permissions.
Directory Listing
Tool to retrieve a listing of files and directories at a given path. use when browsing or filtering file storage directories.
Find User by ID
Tool to retrieve user information by id. use when you need to fetch details for a specific user after you have their objectid.
General Object Retrieval
Tool to retrieve objects from a specified backendless table with filtering, sorting, and pagination. use after confirming the table name and query options. example: "get users where age > 30 sorted by created desc".
Get All Values
Tool to retrieve all values from a map in a specified hive. use when you need to fetch the entire contents of a hive map at once.
Get Backendless Timer
Tool to retrieve information about a specific timer. use when you need to inspect a timer's schedule and next run details by name.
Get Counter Value
Tool to retrieve the current value of a backendless counter. use when you need to inspect an atomic counter's value.
Get File Count
Tool to get the count of files in a backendless directory. use when you need to determine how many items match a filter or include subdirectories.
Get Key Items
Tool to retrieve values for a specified key in a list (all, single, or range). use when you need specific elements or the entire list from a hive key. supports single index retrieval, range retrieval, or full list.
Grant Permission to User
Tool to grant a permission to a user on a specific data object. use when precise access rights must be assigned after verifying the table and object ids. example: "grant find permission to a user for a person record".
Map Put
Tool to set or update key-value pairs in a hive map. use when you need to add or update multiple entries in a hive map.
Move File
Tool to move a file or directory within backendless file storage. use when relocating resources to a new path after verifying source and destination.
Publish Message
Tool to publish a message to a specified messaging channel. use when you need to send notifications or events to subscribers after confirming channel and payload.
Reset Counter
Tool to reset a backendless counter back to zero. use when you need to reinitialize a counter before starting a new sequence.
Revoke Permission from User
destructive
Tool to revoke a permission from a specified user or role on a data table. use when you need to deny a previously granted data-table operation for a user or role in cloudcode after confirming the target.
Set Counter Value
Tool to set a backendless counter to a specific value conditionally. use when you need to ensure the counter only updates if it currently matches an expected value.
Update Backendless Timer
Tool to update schedule or code of an existing timer. use when you need to modify a timer's configuration after retrieval.
Update User
Tool to update properties of an existing backendless user. use when you need to modify user profile fields after login. example: update phonenumber to "5551212".
User Login
Tool to log in a registered user with identity and password. use when you need to authenticate a user before making subsequent requests. example: "login alice@wonderland.com with password wonderland".
User Logout
Tool to log out the currently authenticated user. use when you need to terminate the user session after operations.
User Password Recovery
Tool to initiate password recovery for a user. use when a user requests a password reset after forgetting their password. triggers an email with recovery instructions.
User Registration
Tool to register a new user with email and password. use when creating a user account or converting a guest account to a registered one after collecting credentials. example: register 'alice@wonderland.com' with password 'wonderland'.
Validate User Token
Tool to validate a user session token. use after obtaining a token from login to confirm the session is active.

Setup

Setup guide

11. Open your Switchy workspace and navigate to Settings > Integrations > Developer Tools. 2. Click 'Connect' next to Backendless. 3. Log into your Backendless account and copy your API key from the App Settings > Manage > App Keys section. 4. Paste the key into Switchy's connection dialog and click 'Authorize'. 5. Switchy will validate the key and confirm the connection. 6. Open any Space and type '@Backendless list all timers' to test — the MCP should return your scheduled tasks. 7. To invoke a tool, @mention Backendless and describe the action in natural language (e.g. '@Backendless create a directory called /uploads/2024'). 8. The MCP will confirm each operation and show results inline.

What teammates see: by default, memories from Backendless are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Create Monthly Archive

@Backendless create a directory at /uploads/2024/january and confirm it's ready for new files

Open in a Space →

Schedule Weekly Report

@Backendless create a timer named 'weekly-report' that runs every Monday at 09:00 UTC and executes the analytics summary function

Open in a Space →

Duplicate Config File

@Backendless copy the file at /config/production.json to /config/backups/production-backup.json

Open in a Space →

Provision New Hive

@Backendless create a hive named 'user-sessions' for storing temporary session data

Open in a Space →

Clean Up Old Timers

@Backendless list all timers and show their schedules so I can delete any that haven't run in 30 days

Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Backendless list all files in the /uploads/invoices directory and show me their sizes and upload dates

Output

Here's what I found in /uploads/invoices: • invoice_2024_Q1.pdf (2.3 MB, uploaded Jan 15, 2024) • invoice_2024_Q2.pdf (1.8 MB, uploaded Apr 10, 2024) • invoice_2024_Q3.pdf (2.1 MB, uploaded Jul 22, 2024) • draft_invoice.pdf (450 KB, uploaded Dec 1, 2024) Total: 4 files, 6.65 MB. This is an illustrative example based on typical Backendless file storage responses; actual results depend on your account's directory structure.

Notes

This example demonstrates read-only file browsing. Requires valid API key with file service read permissions. Backendless returns file metadata including size, timestamps, and public URLs. Useful for auditing uploads before performing bulk operations like copying or deletion.

Prompt

@Backendless create a new timer called 'daily-backup' that runs every day at 2 AM UTC to trigger my backup cloud code function

Output

Timer 'daily-backup' created successfully. Configuration: • Schedule: 0 2 * * * (daily at 2:00 AM UTC) • Target: Cloud Code function 'backup' • Status: Active • Next run: Tomorrow at 2:00 AM UTC The timer will invoke your backup function on schedule. This is an illustrative example; actual timer creation confirms the cron expression and function binding in your Backendless app.

Notes

This example shows server-side automation setup. Requires API key with timer creation permissions and an existing Cloud Code function. Backendless timers use cron syntax; incorrect expressions will fail validation. Timers consume backend resources, so monitor execution logs to avoid runaway costs on high-frequency schedules.

Prompt

@Backendless check my Hive store 'user-preferences' and summarize the most common theme settings across all users

Output

Analyzed 847 records in the 'user-preferences' Hive. Here's the theme breakdown: • Dark mode: 68% (576 users) • Light mode: 28% (237 users) • Auto (system): 4% (34 users) Most popular accent color: Blue (412 users). The majority of your user base prefers dark themes, suggesting UI updates should prioritize dark-mode contrast and readability. This is an illustrative synthesis; actual Hive queries return key-value pairs that the AI aggregates.

Notes

This example pairs Backendless Hive data retrieval with AI reasoning to surface insights. Requires read access to the specified Hive store. Hive is Backendless's key-value store; large datasets may hit query limits or require pagination. Best for configuration data or user preferences, not high-throughput transactional workloads.

Use-case deep-dives

SaaS MVP file management

When Backendless wins for early-stage product file handling

A 3-person startup building a document collaboration MVP needs file storage, user auth, and scheduled cleanup jobs without standing up infrastructure. Backendless handles this in one integration: the MCP's 31 tools cover directory creation, file copying, user password resets, and timer-based purges of temp files. Auth is a single API key, so onboarding the team takes under an hour. The trade-off: once you hit 10k active users or need custom S3 policies, you'll outgrow Backendless's abstraction layer and migration gets messy. If you're pre-revenue and need backend logic running by Friday, this MCP delivers without DevOps overhead.

Prototype scheduled data sync

Using Backendless timers for lightweight automation workflows

A 6-person agency prototyping a client dashboard needs nightly CSV exports from their app database to a reporting tool. The Create Backendless Timer and Delete Backendless Timer tools let them schedule server-side scripts without setting up cron or Lambda. They write the export logic once, attach it to a timer, and adjust the schedule as requirements shift. This works until the job needs to process more than a few thousand records or coordinate with external APIs that require retry logic—at that threshold, a dedicated task queue beats Backendless's timer model. For prototypes under 90 days and datasets under 50MB, the timer MCP keeps the stack simple and the agency's ops budget near zero.

Customer portal user provisioning

When Backendless auth tools fit small B2B onboarding flows

A 4-person B2B SaaS team onboards 20-30 new enterprise customers per quarter, each needing a portal login and a dedicated file directory for contract uploads. The Change User Password and Create Directory tools let support reps provision accounts and folder structures from a shared Switchy workspace without touching the codebase. The Create Backendless Hive tool adds key-value storage for per-customer metadata. This breaks down if onboarding volume crosses 100 users per month or if compliance requires audit logs Backendless doesn't surface through the MCP. For low-volume B2B with straightforward user lifecycles, the Backendless MCP keeps provisioning out of the engineering backlog and in the hands of the ops team.

Frequently asked

What does the Backendless MCP do in Switchy?

It connects your Switchy workspace to your Backendless backend, letting AI agents manage files, user accounts, timers, and Hive key-value stores. You can automate tasks like password resets, scheduled jobs, or file organisation without writing code. The MCP exposes 31 tools covering auth, storage, and backend logic — useful if your team already runs app infrastructure on Backendless.

Do I need admin access to connect Backendless?

You need an API key with permissions matching the operations you want to run. Backendless uses API_KEY auth, so whoever generates the key controls what the MCP can do — file writes, user management, timer creation. If your team restricts API keys to admins, you'll need one of them to set up the connection in Switchy.

Can the Backendless MCP create or modify database tables?

No. The MCP focuses on file storage, user password changes, timers, and Hive key-value operations. If you need to query or update relational tables in Backendless Data, use the Backendless REST API directly or write a custom Cloud Code function that the MCP can trigger via a timer.

How does this compare to calling the Backendless API myself?

The MCP saves you from writing API client code for every file-copy or timer-delete request. Your AI agent calls tools like "Delete File" in plain English; Switchy handles the HTTP plumbing. Trade-off: you're limited to the 31 pre-built tools. For complex queries or bulk operations, the raw REST API gives you more control.

Who on the team should connect the Backendless MCP?

Whoever owns your Backendless account and can generate API keys with the right scopes. Typically a backend engineer or DevOps lead. Once connected, any Switchy team member can invoke the tools in their chats — so decide whether you want junior staff triggering file deletes or password changes before you share access.