247 Чат на живо
Docs/Websites
MYASP.NET MCP · BETA

Websites

Beta

Create and manage Windows or Linux websites inside an existing plan. The platform is selected by choosing a planId; website creation does not accept an arbitrary operating-system override.

Typical lifecycle

  1. Call hosting_list_plans and select an existing Windows or Linux plan with capacity.
  2. Call website_create with the plan ID, a 2–20 character ASCII display name, PHP preference, and a new idempotency key.
  3. Call websites_list to obtain the new siteId and temporary URL.
  4. Configure supported site functions, secrets, domains, DNS, and SSL.
  5. Deploy through GitHub Actions using IIS WebDeploy for compatible Windows plans or FTPS for Linux plans.

Site functions

website_get_function returns explicitly allow-listed public fields and current values for a supported control-panel drawer. Use website_update_function with the returned function key, supported action, documented fields, and an idempotency key. Reusing that key with identical arguments replays the recorded outcome; reusing it with different arguments is rejected. GitHub integration, Visitor Statistics, Schedule Tasks, Outgoing Port rules, and browser-only drawers are intentionally excluded.

Platform-specific drawers

Linux sites support directory browsing, compression, cache settings, dynamic IP protection, PHP, Node.js, Python, redirects, IP deny rules, logs, and other compatible common drawers. Windows sites support IIS and ASP.NET drawers, including application pools, .NET Core hosting mode, detailed errors, Script Map, Site Guard, virtual directories, IIS logs, and WebDeploy. A drawer from the wrong platform returns platform_not_supported. The .NET Core hosting-mode operation always targets only the selected site.

Windows application pools

Use application_pool_list with an owned Windows planId to inspect pool-count capacity, allocated RAM, per-pool runtime settings, and website counts. Use application_pool_list_websites to list the sites currently assigned to a returned poolId. application_pool_create creates an additional pool only after NewCP verifies both the plan's pool-count quota and remaining RAM quota. website_change_application_pool moves a website only to a pool owned by the same hosting plan and requires the exact siteId confirmation. These four tools return platform_not_supported for Linux plans.

File Manager ZIP archives

file_manager_create_zip works with Windows and Linux websites. Supply a siteId, a folder path relative to that website's root, 1–50 direct child file or folder names, an output name ending in .zip, and an idempotency key. An empty relativePath targets the website root. Absolute paths, traversal segments, nested item names, and paths outside the selected website are rejected. The operation queues archive creation; use operation_get_status when follow-up status is needed.

FTP and FTPS users

ftp_list_users returns sanitized connection metadata for accessible Windows and Linux plans. Create and update operations require a caller-supplied password, a nonnegative quota value, and a path inside /www. Windows supports read or write permission. Linux FTPS currently requires write permission and keeps the existing login name during updates. Updates and deletes require the exact ftpUserId; the plan's root FTP user cannot be deleted.

Runtime operations

ToolBehaviorConfirmation
website_startStarts the site runtime.Idempotency key
website_restartRestarts the site runtime.Idempotency key
website_stopMakes the site unavailable.Exact site ID
website_deleteDeletes the site through the existing cleanup flow.Exact site ID and file-deletion choice
Deletion is permanent

Inventory the mapped domains, deployment configuration, and application data before deleting a website. Use a new idempotency key for a newly intended deletion.