Developer Tools
bonto.dev
Manages authentication and provides app status information for the Bonto platform.
ENDPOINT 1
https://api.bonto.dev/mcp
MCP server metadata
- Name
- bonto
- Version
- 1.0.0
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
list_appsList all your Bonto apps with their current status, subdomain, and resource limits.
Inferred read-onlyget_appGet detailed information about a specific app including its Docker service status.
Inferred read-onlydelete_appDESTRUCTIVE: Permanently delete an app, its Docker service, volume, and all data including version history.
Potential side effectsstart_appStart a stopped or sleeping app by scaling its Docker service to 1 replica.
Inferred read-onlyupdate_appUpdate an app's settings: name, subdomain, environment variables, resource limits, access control, runtime configuration, and more.
Potential side effectsupload_fileGet a direct upload URL for uploading a binary or text file to an app.
Potential side effectsget_app_statusGet the real-time Docker service status for an app: replica count, whether it is running, and health check status.
Inferred read-onlyset_git_remoteSet or update the upstream Git remote (GitHub/GitLab) for an app.
Potential side effectsget_version_filesList the files and directories at a specific version (commit) of an app.
Inferred read-onlyget_version_file_contentRead the content of a specific file at a past version of an app.
Inferred read-onlyrestore_versionDESTRUCTIVE: Restore an app to a previous version using git reset --hard.
Inferred read-onlylist_packagesList the npm packages currently installed in an app (from package.json) along with the configured Node.js version.
Inferred read-onlyCONNECT 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.
bonto.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.