Bot-Hosting.net

Connect Remote server

claude mcp add --transport http mcp https://bot-hosting.net/api/mcp

{
  "mcpServers": {
    "mcp": {
      "url": "https://bot-hosting.net/api/mcp"
    }
  }
}

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://bot-hosting.net/api/mcp"
    }
  }
}

Settings > Connectors > Add custom connector
URL: https://bot-hosting.net/api/mcp

Tools 72 found in our last check

• deployments_sftp

  SFTP connection details for a deployment: host, port, username and the current password. The password is shown in full, so it needs BOTH deployments:read and deployments:write - a read-only credential cannot reveal it. Returns password: null if none is set yet (the owner generat…

• deployments_list

  List every deployment you can access (owned + shared). The `owned` flag tells them apart. Pass name to find one by name, and brief: true when you only need to pick one: it returns id, name, state, url, runtime and entry file instead of the full record.

• deployments_get

  Fetch a single deployment.

• deployments_update

  Rename a deployment.

• deployments_move

  Move a deployment to another of your projects.

• deployments_delete

  Delete a deployment (instant; teardown runs in the background).

• deployments_create

  Create a deployment (blank, from a public GitHub repo, or a template), or a database by passing its engine as `runtime`. Sized by default to an equal share of the free pool; the result tells you the RAM/CPU it got. A modern web stack needs 512+ MB to npm install (exit 137 = OOM)…

• deployments_getStartup

  Get the startup config: runtime, version, entry file, start command.

• deployments_updateStartup

  Change runtime / version / entry file / start command (queues a rebuild). The start command is a FULL SHELL LINE run at every boot: it can install and build before starting - e.g. 'npm install && npm run build && exec node build/index.js'. There is no other way to run build step…

• runtimes_list

  List available runtimes, services and database engines with their versions.

• deployments_getGit

  Get the linked GitHub source: repo, branch, auto-pull.

• deployments_setAutoPull

  Toggle auto-pull: re-pull the linked repo on every restart.

• deployments_power

  Send a power signal (start / stop / restart / kill). A start or a restart WAITS for the process to settle and hands back the state it reached, the console output it produced and what to do about it: ok:true only means the signal was accepted, the logs say whether the app actuall…

• deployments_logs

  Read the last N lines of the console log, cleaned of colour codes and progress spam. A build or install takes MINUTES: pass waitSeconds (e.g. 25) to wait server-side before reading, instead of calling this again and again - polling in a loop is how a whole conversation gets eate…

• deployments_searchLogs

  Find lines in the console log that deployments.logs does not show: it searches the last 2000 lines (up to 5000) for a word or a regular expression, case-insensitive, and returns each hit with a few lines around it. Use it when the tail looks fine but something went wrong earlier…

• deployments_resources

  Live resource usage: CPU, memory, disk, network and uptime.

• deployments_command

  Write a line to the running process's stdin (a game server console, a REPL). NOT a shell: a web server ignores stdin, so curl / node / npm typed here do nothing, and no output is returned. To run a command (curl, node, npm, grep) use deployments.shell; to request a public URL, d…

• deployments_resize

  Change RAM / CPU / storage allocation (drawn from your plan pool). The deployment restarts to apply it.

• deployments_sync

  Pull the latest code from the linked GitHub repo (restarts it if it was running). Pass branch, and repo if it changed, to FIX a wrong branch after a failed clone: that repoints the deployment and pulls, and is the way to recover, never deleting and recreating.

• deployments_diagnose

  Everything needed to answer "what is wrong with this deployment", in ONE call: live state, RAM and CPU, the cleaned log tail, the startup config, and what the public URL returns. Use this INSTEAD of the deployments.get + deployments.logs + deployments.check + deployments.getStar…

• deployments_apply

  Make edited files live and confirm they work, in ONE call. Use this after writing files instead of deployments.power + deployments.logs + deployments.check. It restarts only when the runtime needs it (a static or PHP site serves straight off the volume, so the restart is skipped…

• files_list

  List a directory inside the deployment volume.

• files_tree

  See the whole project layout in ONE call: every file and folder under a path, indented, with sizes. Use this FIRST when exploring, instead of walking directories with files.list. It returns structure only - read the files you want with files.readMany. Dependency folders (node_mo…

• files_readMany

  Read SEVERAL files in one call. Pair it with files.tree: look at the layout, then pull the handful of files you actually need in a single round instead of one call each. Binary files are reported, never returned as text.

• files_search

  Search the text of the project for a string or regex, like grep. Returns matching lines with their file and line number. Use it to find where something is defined or used instead of reading files one by one.

• files_edit

  Change PART of a file by replacing an exact snippet, leaving the rest untouched. Prefer this over files.write for any edit to an existing file: rewriting a whole file to change a few lines is slow, expensive and loses anything you did not repeat. The snippet must appear EXACTLY…

• files_editMany

  Change SEVERAL places in ONE file in a single call. Use this instead of calling files.edit again and again on the same file: each files.edit is another round trip that re-sends the whole conversation. The edits apply in order, all of them or none: if one snippet is missing or am…

• files_read

  Read a file, or a slice of it. Use offset/limit to page through a long file.

• files_write

  Create or overwrite a text file. A large file does NOT have to fit in one call: send the first part with mode 'overwrite', then the rest with mode 'append'.

• files_writeMany

  Create or overwrite SEVERAL files in ONE call. Use this when creating a project: index.html, style.css and package.json go in a single call instead of one files.write each, which costs a round trip per file. Files are written in the order given; if one fails the call stops and t…

• files_rename

  Rename or MOVE a file or directory: from and to are paths relative to root, and may point into different directories. To move several items into a folder in one call, use files.move.

• files_move

  Move files or folders into a directory of the SAME deployment; the directory is created if missing. Never overwrites: a name already taken there is reported, not replaced. There is no move between two deployments: copying a file across leaves the original, so that is a copy, not…

• files_delete

  Delete one or more files or folders. A copy of each deleted FILE is kept, so files.history / files.restore can bring it back; a deleted folder is gone for good.

• files_mkdir

  Create an EMPTY folder. Not needed before files.move, files.write or files.writeMany: they create the folders they need.

• files_decompress

  Decompress an archive in place. With removeArchive the archive is deleted right after, in the same call, so an upload-and-unpack never leaves the archive behind.

• files_compress

  Compress files into a new archive.

• files_copy

  Duplicate a file in place (the node appends a " copy" suffix). NOT a move: to move or rename, use files.rename.

• files_chmod

  Change a file mode (e.g. "0755").

• files_downloadUrl

  Get a one-time signed URL to download a file.

• files_index

  Flat index of every file under a path with size, mtime and an XXH64 content hash, in ONE call, for sync tools. Honours gitignore patterns. Send the `digest` of a listing you already hold: an unchanged tree answers `unchanged: true` with no entries.

• files_uploadUrl

  Get a one-time signed URL to upload files straight to the node, with no size cap from the panel. POST a multipart form with one or more `files` parts to it: each lands in `path` under its own file name. Valid 15 minutes, single use. Pair with files.decompress to unpack an archiv…

• files_history

  List the saved previous versions of ONE file, newest first. Use it when a change broke something, when the user asks to undo or go back, or before overwriting a file you did not write yourself - then pass a versionId to files.restore. It only covers changes made through this API…

• files_restore

  Put a file back to one of its saved versions: this is the undo. Use it when an edit broke the app or the user asks to revert, and to bring back a file that was deleted. Call files.history first for the versionId. What it replaces is itself saved, so a restore can be undone in tu…

• env_list

  List environment variables. Secret values are masked.

• env_set

  Create or update a user environment variable (applies on next restart).

• env_update

  Update an existing environment variable: rename it (newKey), change its value, or flip its secret flag. Applies on next restart.

• env_delete

  Delete a user environment variable (applies on next restart).

• env_audit

  Compare the environment variables SET on the deployment with the ones the code actually reads. Use it right after writing code that needs configuration, and whenever an app crashes on boot for no visible reason: it names the variables the code reads but nothing sets (missing), t…

• databases_rotatePassword

  Generate a new password for a database deployment and restart it to apply it. The old password stops working at once: every app connecting with it loses access until it is updated, so confirm with the user first. Returns the new password in full. A running database restarts in t…

• backups_list

  List the restore points of a deployment, newest first, and the backup operation in progress.

• backups_get

  Fetch one restore point of a deployment.

• backups_restore

  Restore a restore point. replace: stops the deployment, puts every file back, starts it again if it was running. subfolder: copies the files into /restored-<date>/ without stopping anything. Runs in the background: poll backups.list.

• packages_list

  List packages in the manifest (npm or pip).

• packages_add

  Add or update a package in the manifest.

• packages_remove

  Remove a package from the manifest.

• account_get

  Your profile, credit balance, plan and quota (pool vs used).

• templates_list

  Browse the public template catalogue (any author).

• templates_get

  Full details + public stats of a single template by slug.

• projects_list

  List the projects you own or collaborate on.

• projects_create

  Create a project.

• projects_delete

  Delete a project and all its deployments (owner only).

• deployments_enableDomains

  Assign a subdomain (activate domains). Idempotent.

• deployments_setSlug

  Set the subdomain alias (slug).

• deployments_removeSlug

  Remove the subdomain alias.

• deployments_setCustomDomain

  Attach a custom domain. Returns the DNS verification token.

• deployments_verifyCustomDomain

  Check the DNS for the attached custom domain.

• deployments_removeCustomDomain

  Detach the custom domain.

• deployments_check

  Request this deployment over its public URL and report what came back. Use it after deploying or fixing a site to confirm it really works - "the logs say it started" is not the same as "the page loads". Returns the HTTP status and the start of the body, so a 500 or a stack trace…

• docs_search

  Search the Bot-Hosting documentation. Use this before answering any "how do I" question.

• docs_get

  Read one documentation page in full, by the slug returned from docs.search.

• files_outline

  Map the code WITHOUT reading it: every function, class, export and route with its line number, for one file or a whole folder. Call this BEFORE reading anything, to find where to look, then files.read only the part you need. It costs a fraction of reading the files and it return…

• deployments_shell

  Run a shell command in the deployment's container and get its exit code and output. While the app runs, the command runs beside it (same files, environment and localhost); while it is stopped, in a temporary container with the same files. Use it to install, build, run tests or s…

Details

More cloud and devops servers See all

• OxyPages

  Deploy HTML pages and built web apps (React, Vue, Vite) to a live HTTPS link from your AI agent.

• Privi Call

  One number per AI agent: route MCP calls to any agent, every call sealed in an on-chain log.

• OldWeb Diagnostics

  Public DNS, HTTPS and deployment checks, plus offline email header and delivery-log tracing.

• OldWeb Logs

  Offline log parsing, CI failures, HTTP capture analysis and bounded JSON configuration validation.

• TrainRec

  Your AI assistant logs your meals and workouts, then plans your week from what you did.

• ZeroPhase

  BUD/S prep training: read today's workout, log tasks and PST results from your agent.