REFERENCE

MCP tools

Everything a connected agent can do, and the two things it cannot.

The tools

TOOL	WHAT IT DOES
spocket_deploy	Ship a folder. Same name means a new version.
spocket_upload	Get a URL to PUT a project zip to, for anything past a few files.
spocket_list	Every app with state, memory and uptime.
spocket_status	One app in detail, including the live container state.
spocket_logs	Recent output, up to 500 lines.
spocket_search_logs	Find lines matching a term, with context.
spocket_restart	Restart, or start if it is already down.
spocket_stop	Stop without giving up the slot.
spocket_start	Start a stopped app.
spocket_set_env	Set or replace environment values.
spocket_rollback	Return to an earlier version.
spocket_migrate	Move an app to a different machine.
spocket_nodes	Which machines your apps are on.
spocket_account	Plan, slots used, trial status.
spocket_customers	For resellers: each customer, their app count, and which apps are unhealthy.
spocket_platform_usage	For resellers: apps against capacity, what is billed, and which API keys are live.
spocket_urls	Every URL an app answers on: webhook and custom domains.
spocket_add_domain	Point your own domain at an app; returns the DNS to create.
spocket_verify_domain	Re-check DNS for a domain you added.
spocket_remove_domain	Detach a domain and release its certificate.
spocket_delete	Permanently delete an app. Asks you to confirm by name first.

Deploying a real project

An agent can pass files inline, which is fine for a single script or a one-page site. Beyond that it stops being practical: every byte has to travel through the agent’s own context, so a build output or a folder of images is effectively undeployable that way.

For anything larger the agent uploads a zip instead, and the bytes go straight to storage without passing through the conversation:

Zip the project, skipping node_modules, .git and .env — dependencies are installed here, and secrets belong in the environment.
Call spocket_upload for a URL and an upload_id.
PUT the zip to that URL. The URL is the credential, so there is no auth header.
Call spocket_deploy with upload_id instead of files.

The URL lasts fifteen minutes and one upload, and the ceiling is your plan’s disk allowance. Five uploads can be open at once.

An upload belongs to the account that asked for it. An upload_id from somewhere else is refused, and refused identically to one that never existed — so it cannot be used to find out whether someone else’s upload is there.

Moving an app

Rarely needed — a crash restarts on its own, and a machine that fails is evacuated automatically. But if an app is on a machine that is misbehaving, it can be moved:

TEXT

Move mod-app to another machine.

The app is rebuilt from its current version somewhere with room, and the old container is removed only once the new one exists — so a failed move leaves it exactly where it was.

You cannot choose the destination. Which machine an app lands on is a balancing decision, and letting it be picked would let one account concentrate load on a machine other people are using.

What agents cannot do

Read an environment value back. Write-only, with no exception for automated callers.
Delete an app. Deletion is permanent, so it stays a human decision in the panel.
See anything about the machines beyond which ones your own apps are on — not how many exist, nor how full they are.
Choose which machine an app is deployed or moved to.

Both limits hold regardless of what the agent is asked to do.

Revoking access

Every connected tool is listed in Settings with when it last called us. Revoking one takes effect immediately — the token stops working on the next request, and reconnecting requires your approval again.

Revoke anything you no longer use. An unused connection is still a live credential.

PREVIOUSRestarts and uptime NEXTRuntimes and limits