Let your AI agent run and look after your services

Keep the API running as a service that starts on boot, schedule the 3 AM backup, or find out why the worker keeps crashing by reading its logs: ask in one sentence and your agent handles it on systemd, no unit file or crontab to write by hand.

What you'd ask your agent

In plain language, the way you'd say it to a person

  • “Run the API as a systemd service that starts on boot”
  • “The worker keeps crashing: check the systemd logs and tell me what's going on”
  • “Schedule the database backup every day at 3 AM”

The tools in this domain (12)

Generated live from the server itself

Pulled from the MCP server itself on every build. Descriptions are in English because that is what the agent reads.

Cloud – Scheduled tasks

  • controlar_tarea_vps: Runs an action on a scheduled task: 'start' runs its command once, right now; 'stop' interrupts that run; 'enable'/'disable' toggle the automatic schedule. Note this set has no 'restart' — unlike controlar_servicio_vps,…
  • crear_tarea_vps: Creates a scheduled task on a VPS. schedule uses systemd OnCalendar syntax (e.g. '*-*-* 02:00:00' for daily at 2am, or shortcuts like 'daily'/'hourly'/'weekly'). start: run it once immediately in addition to scheduling…
  • editar_tarea_vps: Updates a scheduled task's command and/or schedule (at least one required). Internally this deletes and recreates the task — if enabled, it's re-enabled after.
  • eliminar_tarea_vps: Deletes a scheduled task from a VPS. No protected-name guard exists for tasks (unlike systemd services).
  • listar_tareas_vps: Lists scheduled tasks (systemd timers) configured on a VPS. (read only)
  • ver_tarea_vps: Full detail of a scheduled task on a VPS: service+timer content, status, next/last run. (read only)

Cloud – Systemd services

  • controlar_servicio_vps: Runs a systemctl action on a systemd service inside a VPS. 'enable'/'disable' only change whether it starts on boot; they don't start or stop it now. Unlike delete, this has no protected-service guard — it can…
  • crear_servicio_vps: Creates a new systemd service inside a VPS from a raw unit-file content string. Same power a human has via the frontend — no extra validation of the unit file content. Creating always starts the unit and enables it at…
  • editar_servicio_vps: Overwrites a systemd service's unit file content (full replace) inside a VPS.
  • eliminar_servicio_vps: Deletes a systemd service inside a VPS (stops, disables, removes the unit file). A small set of critical service names (ssh, nginx, docker, mysql, etc.) are protected and can't be deleted this way.
  • listar_servicios_vps: Lists systemd services running/configured inside a VPS. (read only)
  • ver_servicio_vps: Full detail of a systemd service inside a VPS: unit file content, live status. (read only)

The same thing, from the panel

Everything the agent does is also a few clicks away in the VPS panel.

How do you connect?

Three steps, and the agent handles two of them

  1. You give your agent the MCP server address — it registers itself
  2. The agent opens an authorization link in your browser
  3. You pick the scope and approve. Done: it works on your behalf

Copy, paste, done

Copy this message and paste it to your AI agent — it connects on its own and will only walk you through the part you have to do (approving access in your browser).

Connect to the ArduMaker MCP server at https://mcp.ardumaker.com/mcp (Model Context Protocol, OAuth 2.1). Add it as a remote MCP server and walk me step by step only through what I need to do myself, such as approving access in the browser.
  • Automatic discovery via OAuth metadata
  • Dynamic Client Registration (DCR)
  • PKCE — no secrets to leak
  • The session renews itself: connect once

Manual configuration (Claude Desktop, Cursor, etc.)

{
  "mcpServers": {
    "ardumaker": {
      "url": "https://mcp.ardumaker.com/mcp"
    }
  }
}

Connect your agent

Two steps per client. No API keys: you approve access in the browser and you're done.

  • Claude: Claude → Settings → Connectors → «Add custom connector». Paste the server URL and approve access in the browser.
    https://mcp.ardumaker.com/mcp
  • ChatGPT: ChatGPT → Settings → Apps & connectors → enable developer mode. Create a connector with the server URL and authorize it.
    https://mcp.ardumaker.com/mcp
  • Gemini CLI: In Gemini CLI run the command below. Approve access when the browser opens.
    gemini mcp add --transport http ardumaker https://mcp.ardumaker.com/mcp
  • Cursor: Save this block in your project's .cursor/mcp.json. Approve access when Cursor opens the browser.
    // .cursor/mcp.json
    { "mcpServers": { "ardumaker": { "url": "https://mcp.ardumaker.com/mcp" } } }
  • VS Code / Copilot: In VS Code: «MCP: Add Server» → HTTP, or save this block in .vscode/mcp.json. Approve access when the browser opens.
    // .vscode/mcp.json
    { "servers": { "ardumaker": { "type": "http", "url": "https://mcp.ardumaker.com/mcp" } } }
  • MCP: Any MCP client: point it at the server URL (HTTP, OAuth 2.1). Approve access when the browser opens.
    https://mcp.ardumaker.com/mcp

What your agent can do

Practically everything you do yourself, under the same rules and permissions

  • VPS and commands: Create and control servers, run commands, read logs and metrics, manage Linux users

    For example, you ask it:

    • “Spin up a mid-tier VPS and hand it to me with Docker already installed”
    • “Find out why the server is at 90% RAM and tell me which process is eating it”
    • “Pull the last 200 lines of the nginx log from the production server”
    • “Create a Linux user for the new dev with access only to their own folder”
  • Domains, DNS and nginx: Your own domains and their DNS records, nginx configuration, reverse proxies and port forwards

    For example, you ask it:

    • “Point this domain at the staging VPS and turn on SSL”
    • “Add the TXT record Google is asking for to verify the domain”
    • “Set up a reverse proxy to port 3000 for the new app”
    • “Check my domain's DNS and tell me whether the nameservers point where they should”
  • Email: Mail domains, mailboxes, aliases, filters and folders — plus reading and sending messages

    For example, you ask it:

    • “Create a mailbox for the new dev with a 5 GB quota”
    • “Set up a contact@ alias that fans out to the whole team”
    • “Check whether anything from billing arrived this week and summarize it”
    • “Configure the mail DNS for the new domain and verify it's correct”
  • Databases: PostgreSQL and MySQL: explore the schema, query, insert, edit rows and run DDL

    For example, you ask it:

    • “Show me what tables the production database has and how they relate”
    • “Count how many orders came in yesterday and group them by status”
    • “Add a cancellation-date column to the customers table”
    • “This query is slow: explain the plan and tell me which index is missing”
  • Projects and team: Stages, tasks, checklists, calendar, meetings, attachments and audit trail

    For example, you ask it:

    • “Load the tasks for the new stage and split them by who's actually available”
    • “Which task should I pick up now, given what's already unblocked?”
    • “Book a one-hour meeting with the team when everyone is free”
    • “Summarize what moved on the project this week from the activity log”
  • GitHub deploys: Link repos, redeploy, and read the commits and logs of every deployment

    For example, you ask it:

    • “Redeploy the frontend repo and tell me if the build fails”
    • “Which commit is running in production right now?”
    • “Show me the log of the last deploy that errored out”
  • WordPress: Sites, Elementor, WooCommerce, plugins, SEO, backups, staging and moves, on your own VPS

    For example, you ask it:

    • “Create a WooCommerce store on my VPS with 3 products and publish it at store.mydomain.com”
    • “Take a backup and then change Elementor's global colors”
    • “Bring my site from this UpdraftPlus backup”
    • “Try the redesign on staging and, if it looks good, publish it to production”
  • AI and search keys: Router IA keys and Search API tokens: create them, revoke them and check usage

    For example, you ask it:

    • “Create a Router IA key for the new project and hand it to me”
    • “How much have I spent on searches this month?”
  • Blog and content: Write, translate and publish blog posts, with their sections and images

    For example, you ask it:

    • “Write a post about the launch and translate it into Spanish and Portuguese”
    • “Publish the draft that's been sitting there since last week”
  • SSH tunnels: Tunnel receivers and initiators, keys, and the state of every connection

    For example, you ask it:

    • “Set up a tunnel so I can reach the database from my machine”
    • “Tell me whether the client's tunnel is still up”
  • Workspace and usage: Contracted services, usage for the period, and the workspace's verification status

    For example, you ask it:

    • “What services am I paying for, and how much has this month run up?”
    • “Tell me what's still missing for the workspace to be verified”
  • Issue reporting: The agent can report a problem when something breaks, and look up its reports

    For example, you ask it:

    • “Report this failure with the details of what you were doing”
    • “Which issues have I reported, and what state are they in?”

See the full reference

The tools in this domain · See everything the MCP does

How it works under the hood

The technical documentation for what this page covers: what each tool does, what changes, how to verify it and which MCP tools operate it.

  • Docker: Docker daemon on the VPS and apps as Compose projects: image, private registry, repo or Compose, with optional HTTPS.
  • n8n: n8n in queue mode on Docker, with workers, task runners, its own PostgreSQL and Redis, HTTPS and updates with backup.
  • systemd services: Create, edit, control and delete systemd services on a VPS, with rollback if they fail to start and journal logs.
  • Scheduled tasks: Commands on a schedule on the VPS through a systemd service and timer, with minute shortcuts, manual runs and logs.

All the documentation