Styr Wallnode från Claude och dina egna verktyg

The account behind this API key: email, Wallnode username (part of every address), whether it is an admin, the key's scope, instance limit and current plan. Call this first.

Lists the active Wallnode plans with price (SEK per interval, from price_cents / 100), limits (instances, apps, databases, storage, vCPU, RAM) and features. Plans are informational: only the account's instance limit (see wallnode_whoami) is enforced. Use wallnode_get_billing for the current plan.

The account's current subscription (plan, status, period end) and its saved custom server configuration (vCPU, RAM, storage, add-ons, price in SEK, status). Read only: plans are changed in the Wallnode app.

The account's activity log, newest first: what happened (action such as instance.created, backup.restored, domain.activated), on which resource, when and with what metadata. Filter with action_prefix (e.g. 'instance.' or 'backup.'). Admins may pass user_id or all_users: true. Returns { items, total_count, has_more, next_offset }.

Lists the database records of the account (name, engine, version, status, host, port, size). These are records only: Wallnode does not provision real database servers for them yet, so do not assume they accept connections. Passwords are never returned.

Lists the account's API keys (id, name, prefix, scope, created, last used, expires, revoked). The key secrets are never shown. Creating keys is only possible in the Wallnode app.

Revokes an API key permanently by id (from wallnode_list_api_keys). IRREVERSIBLE: anything using that key stops working immediately. Revoking the key used for this very connection ends this session.

Lists the services on this account, newest first, with stored status and address. service is one of: web (a web app deployed from GitHub, including Lovable projects), wp (WordPress), n8n (automation). Filter by service and status. Admins can pass all_users=true to list every customer's instances with owner email. status is the stored value and can lag; use wallnode_get_instance_status for the live state.

Full detail for one instance: stored fields, live status from the server, the active custom domain (if any) and, for web apps, the latest deployment. For deployment history use wallnode_list_deployments; for CPU/memory use the stats tools.

Asks the server for the live state of one instance: status (running, starting, installing, stopped, failed, missing, unknown), ready flag and any error. Also syncs the stored status. Use it to wait for a new instance or deployment to become ready.

Creates an n8n automation server and returns its address (status starts as provisioning; poll wallnode_get_instance_status until ready). Counts against the account's instance limit. If an instance with the same address already exists it is returned unchanged. For WordPress use wallnode_create_wordpress_instance; for GitHub web apps use wallnode_create_web_app.

Creates a WordPress site and returns its address and the WordPress admin password. The password is shown ONLY in this response and is never stored, so pass it on to the user immediately (wallnode_reset_wordpress_password can issue a new one). Installation runs in the background for a few minutes; poll wallnode_get_instance_status. Counts against the instance limit.

Changes the display name of an instance (1-80 characters). Only the name in the app changes, never the address.

Starts a stopped instance. Use wallnode_get_instance_status afterwards to confirm it is running.

Stops a running instance. The service goes offline (its data is kept) until wallnode_start_instance is called.

Restarts an instance. Short downtime. For a web app this restarts the running container only; use wallnode_deploy to rebuild from the latest commit.

Brings an instance up to date. n8n and WordPress: pulls the newest image and restarts (short downtime). Web apps: rebuilds and redeploys the latest commit of the tracked branch (same as wallnode_deploy) and returns the deployment.

Creates a new WordPress admin password for a WordPress instance and returns it. The old password stops working. The new password is shown ONLY in this response and is not stored.

PERMANENTLY deletes an instance: the container, its data, custom domain, environment variables and deployment history. This cannot be undone (take a backup first if needed). confirm_name must equal the instance's current name exactly (see wallnode_get_instance).

Shows whether the GitHub integration is configured and which GitHub accounts/organisations are linked to this Wallnode account (installation_id, account, suspended). Returns the install and authorize URLs. Linking a GitHub account or installing the Wallnode GitHub App cannot be done through this server: it needs the user's own OAuth consent in a browser, so give the user the install_url and ask them to complete it on wallnode.se, then call this tool again.

Lists repositories the linked GitHub installation gives Wallnode access to, most recently pushed first. Optional text filter on the name. Returns full_name (owner/name), default_branch, private. Use with wallnode_list_github_branches and wallnode_create_web_app.

Lists the branches of a repository (first 100) that is reachable through a linked GitHub installation.

Analyses a repository branch and returns the detected framework, package manager and suggested install/build/start commands, output dir, port, plus the names (never values) of environment variables found in .env.example style files. Run it before wallnode_create_web_app to pick build_config and know which env vars to set.

Creates a web app from a GitHub repository branch and starts its first deployment. The address is web.<username>[-suffix].walldy.com. Counts against the instance limit. Returns the instance and the initial deployment; follow progress with wallnode_get_deployment_logs and wallnode_get_instance_status. Get installation_id, repo and branch from the github tools; use wallnode_detect_repo to choose build_config. env values are stored encrypted and cannot be read back.

Admin only. Refreshes which repositories the linked GitHub installations give access to, straight from GitHub. Use it after creating a new repository (for example with the GitHub CLI) and before wallnode_create_web_app, instead of the browser "Synka åtkomst" button. Optional installation_id limits it to one installation.

Lists deployments of a web app, newest first, with status (queued, building, deploying, ready, failed, canceled), commit and error. Use the id with wallnode_get_deployment_logs, wallnode_rollback_deployment (needs status ready) or wallnode_cancel_deployment.

Builds and deploys the latest commit of the tracked branch of a web app now. Queued older deployments are superseded. Returns the new deployment; follow it with wallnode_get_deployment_logs. To redeploy an older version use wallnode_rollback_deployment.

Reads the build/deploy log of a deployment. Pass offset 0 first, then pass the returned next_offset to continue until done is true. Long chunks are cut to the newest 16000 characters (truncated=true). Also returns the deployment status.

Redeploys an earlier successful deployment (status ready) of a web app, reusing its built image when it still exists. The current live version is replaced. Find candidates with wallnode_list_deployments status=ready.

Cancels a queued or running deployment. Does nothing if it has already finished. The currently live version keeps running.

Changes settings of a web app: tracked branch, auto_deploy on push, display name and build_config (replaces the whole build config, so send the complete object). Set redeploy=true to apply build changes by starting a new deployment. Provide at least one setting.

Lists the names (and created/updated times) of the environment variables stored for an instance. Values can never be read back, by design. Use wallnode_set_env_vars to add or replace values.

Creates or replaces environment variables on an instance from a name to value map (max 200 per instance, 32 KiB per value). Values are stored encrypted and cannot be read back; existing variables with other names are left alone. Web apps need a redeploy to pick the change up (set redeploy=true or call wallnode_deploy).

Permanently deletes environment variables by name from an instance. The values are gone and cannot be recovered. Web apps need a redeploy for the removal to take effect.

Shows the custom domain of a web or WordPress instance, with a live DNS check. Returns the domain state: status (pending, active or error), the DNS records you must create at your registrar or DNS provider (each with a check result), the detected DNS provider and whether the domain is Cloudflare proxied (if so, set the records to DNS only, grey cloud). The A record value is the IP of the Wallnode server the instance runs on. Wallnode cannot change DNS for you. Only web and wp instances support custom domains.

Attaches a custom domain to a web or WordPress instance (one domain per instance). The domain starts as pending: create the DNS records in the result, then call wallnode_check_domain. Returns the domain state: status (pending, active or error), the DNS records you must create at your registrar or DNS provider (each with a check result), the detected DNS provider and whether the domain is Cloudflare proxied (if so, set the records to DNS only, grey cloud). The A record value is the IP of the Wallnode server the instance runs on. Wallnode cannot change DNS for you.

Re-checks the DNS records of the instance's custom domain. When every record is correct the domain is activated automatically (HTTPS follows shortly after). Returns the domain state: status (pending, active or error), the DNS records you must create at your registrar or DNS provider (each with a check result), the detected DNS provider and whether the domain is Cloudflare proxied (if so, set the records to DNS only, grey cloud). The A record value is the IP of the Wallnode server the instance runs on. Wallnode cannot change DNS for you.

Decides what the free *.walldy.com address does once a custom domain is attached: 'redirect' sends visitors to the custom domain, 'off' makes the free address stop serving the site. Requires an existing custom domain. Returns the domain state.

Detaches the custom domain from the instance and removes it from the server. The site stays reachable on its free *.walldy.com address. Reversible: the domain can be added again with wallnode_add_domain (DNS records at your provider are not touched).

Analyses any public domain from public DNS data: registrar, name servers (DNS provider), mail setup (MX, SPF) and web host. The domain owner (registrant) is not returned: registries hide it. Reads only public data and stores nothing. Rate limited. Use wallnode_get_domain for domains attached to your own instances.

Lists the backups of an instance (automatic and manual, at most 4 are kept, oldest are replaced). Returns { max, backups: [{ id, type, created_at, size_bytes }] }. Backup ZIP downloads cannot be returned over MCP: download them in the Wallnode app (Instance, Backups).

Creates a manual backup of an instance now. Only 4 backups are kept per instance, so the oldest one may be replaced. Returns the new backup (id) or { ok: true }. Backup ZIP downloads cannot be returned over MCP: download them in the Wallnode app (Instance, Backups).

Restores an instance from a backup. IRREVERSIBLE: all current data of the instance is overwritten and the instance restarts. Consider wallnode_create_backup first. Requires confirm: true.

Permanently deletes one backup of an instance. IRREVERSIBLE. Requires confirm: true.

Live resource use of one instance right now: running, status, started_at, restart_count, cpu_percent, memory (used/limit MB and percent), network and disk I/O in MB, process count. Use wallnode_get_usage for history (averages and peaks).

Resource usage per instance from snapshots taken every 10 minutes: the latest CPU, RAM and network values plus average and maximum over the last `hours` (1 to 720, default 24). Covers your own instances. Admins may pass user_id for one user or all_users: true for everyone. Use wallnode_get_instance_stats for a live reading.

Admin only. Host-level usage of the Wallnode server from snapshots: the latest CPU, load, RAM, disk, network and container count, plus average and maximum over the last `hours` (1 to 720, default 24).

Admin only. Live overview of the whole server: host CPU/RAM/disk, every instance with owner, usage and whether it exists in the app, containers that exist only on the server (unassigned_containers, candidates for wallnode_admin_remove_orphan), instances the app lists that are missing on the server, and the last hours of host history. Can be large.

Admin only. Lists user accounts with email, signup and last sign-in time, username, instance limit and number of instances. `search` filters on email (substring). Returns { items, total_count, has_more, next_offset }.

Admin only. Sets how many instances (all services together) a user may create. 0 blocks new instances; existing ones are not touched. Returns { ok, instance_limit }.

Admin only. Sets the runtime memory (MB) and CPU limit for one GitHub web app, overriding the server default. Pass null to go back to the default. Takes effect on the next deploy, so run wallnode_deploy afterwards. Returns { ok, memory_mb, cpus }.

Admin only. Changes a user's Wallnode username (lowercase letters, digits and dashes, 2 to 30 characters, must be unique). Existing instances keep their old addresses; only new instances use the new username.

Admin only. Emails a password reset message to an existing user so they can choose a new password themselves. The reset link is never shown here. Passwords cannot be set through this server.

Admin only. Deletes a container set that exists on the server but has no instance in the app (see unassigned_containers in wallnode_admin_get_stats). IRREVERSIBLE: its data on the server is gone. Refused if the app still has an instance with that username and service. Requires confirm: true.

Admin only. Permanently deletes a user account and its app records (profile, instance rows, tickets and so on). IRREVERSIBLE. It does NOT remove the user's containers on the server: delete their instances first (wallnode_delete_instance) or clean up afterwards with wallnode_admin_remove_orphan. You cannot delete yourself. Requires confirm: true.

Lists support tickets, newest activity first. Returns { items, total_count, has_more, next_offset } with id, subject, status, priority, category, instance_id and timestamps. Admins can pass all_users: true to see every user's tickets (with the requester's email). Use wallnode_get_ticket for the conversation.

Returns one support ticket with its description and all messages in order (author_type is user, admin or system). Admins can read any ticket.

Opens a support ticket with the Wallnode team (they are notified by email). Returns the ticket id. Link an instance with instance_id when the problem concerns one. Follow up with wallnode_get_ticket or wallnode_reply_ticket.

Adds a message to a ticket. Ticket owners and admins can reply. Without `status` the ticket becomes open after a customer reply and waiting after an admin reply, as in the app. Pass status (open, in_progress, waiting, resolved, closed) to set it explicitly, e.g. closed or resolved when the matter is done.