Server4Agent MCP server

What tools does Server4Agent expose? (38)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

• create_serverProvision a sized server box.
• list_servers`[read-only]`: List your servers with their tier, kind, status, project sharing, and current project count.
• get_server`[read-only]`: Get a server's tier, kind, status, capacity, project count, and project sharing.
• update_server`[destructive]`: Update a server's nickname, region, or how much its projects may see of each other.
• control_server`[destructive]`: Pause a server (stop), resume it (start), or reboot it (restart).
• delete_server`[destructive]`: Tear down a server and every project on it.
• get_usage`[read-only]`: Get the account's AI spend and budget: how much has been spent this billing period, the plan's included credits, any budget cap, and whether new tasks are blocked (with the reason).
• list_templates`[read-only]`: List the available project starters.
• create_projectCreate a project on a server: the home for one web page, site, app, API or bot, with its own URL at <slug>.apps.server4agent.com.
• list_projects`[read-only]`: List projects.
• get_project`[read-only]`: Get a single project: name, slug, description, public URL, listen port, run plan, timestamps.
• update_project`[destructive]`: Rename a project, update its description, change visibility, link access or lifecycle, or correct its run plan.
• init_projectStart or resume bring-up for a project seeded from a git/archive source: the on-server agent installs dependencies, starts the app, and confirms it responds.
• export_projectPackage a project into a portable bundle and return a time-limited download link.
• import_projectRecreate a project on a server from a bundle that export_project produced, here or on another Server4Agent deployment.
• cleanup_project`[destructive]`: Clean up an ephemeral project once its task is done.
• delete_project`[destructive]`: Delete a project.
• set_secret`[destructive]`: Create or update a secret (an env var, key → value) on the account.
• list_secrets`[read-only]`: List the account's secrets: keys, notes, and where each is bound (servers/projects).
• attach_secret`[destructive]`: Bind a secret to a scope so runs there see it as an env var.
• delete_secret`[destructive]`: Delete a secret and all of its bindings.
• start_app`[destructive]`: Start a project's app and keep it running: the step that puts a project online after its files are written.
• promptSend a freeform prompt to the on-server agent.
• exec`[destructive]`: Run a shell command on the server and return its output.
• get_run`[read-only]`: Get a run's status, its latest progress note, the agent's final response, and what it changed in the workspace (commit, branch, files).
• get_logs`[read-only]`: Read the latest log tails from a server: one entry per log file that a project's processes have written (each long-running process appends to .server4agent/<name>.log in its project folder).
• list_files`[read-only]`: List paths in the server's workspace.
• read_file`[read-only]`: Read a file from the server's workspace.
• write_file`[destructive]`: Write or overwrite a file in the server's workspace.
• delete_file`[destructive]`: Delete a file from the server's workspace.
• get_download_urlMint a time-limited link to download one file from the server's workspace, e.g. after generating a report or converting a file, hand this URL back to the user instead of the raw content.
• start_buildHave the on-server agent build a web page, site, app or API from a plain-language goal.
• get_build`[read-only]`: Get a build's status.
• deployDeploy a project to its live public URL at <slug>.apps.server4agent.com: the last step in putting a web page, site, app or API online.
• start_tuningFix an agent from an evaluation platform's report.
• get_tuning_sessionGet a tuning run's status and the agent run behind it.
• list_tuning_sessions`[read-only]`: List tuning runs on this account, newest first.
• report_tuning_resultTell the evaluation platform what a tuning run changed, and where the fixed build is reachable.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• Last commit today — Actively maintained.
• Repository created today — Very new project with little track record yet.
• 0 GitHub stars — Very little community usage so far.
• No license declared — Without a license the code is not legally reusable in a commercial project.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%100%

  Last commit 0 days ago.

• Adoption20%0%

  0 stars.

• Transparency20%75%

  3/4: ✓ public source repo, ✗ declared license, ✓ documentation, ✓ discoverable tool list.

• Provenance15%75%

  Links to its own repository; package linkage unverified.

• Packaging15%75%

  Remote endpoint; authentication requirements not declared.

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

Excerpt — the full document is on GitHub.

Maintain Server4Agent? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![Server4Agent on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-server4agent-server4agent)](https://mcp-skills-hub.vercel.app/mcps/com-server4agent-server4agent)