← Registry

Developer Tools

bonto.dev

Manages authentication and provides app status information for the Bonto platform.

1 endpoint37 known toolsFirst detected May 10, 2026Last detected August 19, 2026

ENDPOINT 1

https://api.bonto.dev/mcp

No auth detected

MCP server metadata

Name
bonto
Version
1.0.0
Capabilities
tools.listChanged
Server instructions

Bonto — deploy and manage Node.js apps from your AI assistant. Authentication — token persistence: When you successfully authenticate (via check_login), the response includes a JWT token. You MUST save this token to a persistent local file so future sessions can skip the login flow. - Save to a file called "bonto_auth.json" next to your MEMORY.md file (in the same directory as your auto-memory or project config) - File format: { "token": "<jwt>", "username": "<username>", "savedAt": "<ISO date>" } - At the START of every new session, read "bonto_auth.json" from the same directory as your MEMORY.md — do NOT glob or search for it. If it exists, call set_token with the saved token to restore your session silently — do NOT ask the user to log in again. - If set_token fails (token invalid/expired), delete the file and fall back to the full login flow below. Getting started (only if no saved token exists): 1. Call login to get an authorization code 2. Ask the user to open the URL shown and click Authorize 3. Call check_login with the code — repeat until status is approved 4. Save the returned token to your local bonto_auth.json file for future sessions Once authenticated: - list_apps → see your apps - create_app → create a new app (it starts running immediately) - write_file → deploy code by writing files (app auto-restarts on file changes) - search_files → grep-like search across all files in an app (supports context lines -A/-B/-C, glob filtering, output modes: content/files_with_matches/count) - read_file → read a file, optionally with line offset/limit for large files - get_logs → check console output for errors - restart_app → force restart if needed Git & versions: - git_info → get the Git clone URL for push-to-deploy - list_versions → browse version history (auto-saved snapshots) - restore_version → roll back to a previous version (destructive — confirm with user first) Package management: - search_packages → search the npm registry - install_packages / remove_package → manage npm dependencies - list_packages → see installed packages and Node.js version - set_node_version → switch between Node 18, 20, or 22 - get_install_status → poll npm install progress IMPORTANT — destructive operations: Tools marked DESTRUCTIVE (delete_app, restore_version, delete_file for directories) permanently destroy data. ALWAYS confirm with the user before calling them. Notes: - Apps auto-sleep after 30 min of inactivity, wake automatically on request - Files are limited to 1MB each - Subdomains: 3-30 chars, lowercase letters/numbers/hyphens - The 'app' parameter on most tools accepts either the app UUID or subdomain

Known tools 37

login

Generate a 6-digit device code for authentication.

Inferred read-only
set_token

Restore an authenticated session using a previously saved JWT token.

Inferred read-only
check_login

Check if the device login code has been approved.

Inferred read-only
list_apps

List all your Bonto apps with their current status, subdomain, and resource limits.

Inferred read-only
get_app

Get detailed information about a specific app including its Docker service status.

Inferred read-only
create_app

Create a new Bonto app.

Potential side effects
delete_app

DESTRUCTIVE: Permanently delete an app, its Docker service, volume, and all data including version history.

Potential side effects
start_app

Start a stopped or sleeping app by scaling its Docker service to 1 replica.

Inferred read-only
stop_app

Stop a running app by scaling its Docker service to 0 replicas.

Inferred read-only
restart_app

Restart a running app.

Inferred read-only
update_app

Update an app's settings: name, subdomain, environment variables, resource limits, access control, runtime configuration, and more.

Potential side effects
list_files

List the contents of a directory in an app.

Inferred read-only
read_file

Read the contents of a file in an app.

Inferred read-only
write_file

Create or update a file in an app.

Potential side effects
delete_file

DESTRUCTIVE: Delete a file or directory in an app.

Potential side effects
create_directory

Create a directory in an app.

Potential side effects
upload_file

Get a direct upload URL for uploading a binary or text file to an app.

Potential side effects
search_files

Search for text across all files in an app.

Inferred read-only
rename_file

Rename or move a file or directory in an app.

Inferred read-only
get_logs

Get console output (stdout + stderr) for an app.

Inferred read-only
get_app_status

Get the real-time Docker service status for an app: replica count, whether it is running, and health check status.

Inferred read-only
get_app_metrics

Get CPU, memory, and network stats for a running app container.

Inferred read-only
git_info

Get the Git clone URL and authentication instructions for an app.

Inferred read-only
set_git_remote

Set or update the upstream Git remote (GitHub/GitLab) for an app.

Potential side effects
remove_git_remote

Remove the upstream Git remote from an app.

Potential side effects
git_pull

Pull the latest changes from the upstream Git remote into the app.

Inferred read-only
git_push

Push the app's commits to the upstream Git remote.

Inferred read-only
list_versions

List the commit history (version snapshots) for an app.

Inferred read-only
get_version_files

List the files and directories at a specific version (commit) of an app.

Inferred read-only
get_version_file_content

Read the content of a specific file at a past version of an app.

Inferred read-only
restore_version

DESTRUCTIVE: Restore an app to a previous version using git reset --hard.

Inferred read-only
search_packages

Search the npm registry for packages.

Inferred read-only
list_packages

List the npm packages currently installed in an app (from package.json) along with the configured Node.js version.

Inferred read-only
install_packages

Install one or more npm packages in an app.

Inferred read-only
remove_package

Remove an npm package from an app.

Potential side effects
set_node_version

Change the Node.js runtime version for an app (18, 20, or 22).

Inferred read-only
get_install_status

Check the status of an ongoing npm install operation.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bonto]
url = "https://api.bonto.dev/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "bonto": {
      "type": "http",
      "url": "https://api.bonto.dev/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: bonto
Remote MCP URL: https://api.bonto.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bonto": {
      "url": "https://api.bonto.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "bonto": {
      "type": "http",
      "url": "https://api.bonto.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "bonto",
  "transport": "streamable-http",
  "url": "https://api.bonto.dev/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for bonto.dev was fetched 2026-08-28T14:51:48.097Z.

Trust status Neutral

bonto.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.