Existing hosting plans
MCP does not buy or provision plans. hosting_list_plans returns the plans already available to the authenticated account, including Windows or Linux platform information and capacity.
MYASP.NET MCP · BETA
BetaCore Concepts
A few conventions make every Beta tool predictable: opaque resource IDs, plan boundaries, platform-aware capabilities, idempotent writes, confirmations, and sanitized results.
Opaque resource identifiers
Use IDs returned by list tools—such as siteId, planId, databaseId, and domainId. Do not construct, decode, or persist assumptions about their internal meaning.
Platform-aware tools
Windows and Linux plans share the common website lifecycle, while platform-specific settings differ. For example, IIS application-pool and WebDeploy operations apply only to compatible Windows plans.
Idempotency
Every write accepts an idempotencyKey. Generate a unique value for a new operation and reuse the same value only when retrying the exact same request.
Exact confirmation
Risky changes require fields such as confirmSiteId or confirmDatabaseId. Permanent deletion also requires an explicit data-loss acknowledgement.
Sanitized results
Responses omit internal account relationships, server implementation details, unrestricted paths, stored passwords, and other secrets. Missing and foreign resources use the same non-disclosing behavior.
Standard result envelope
JSON
{
"success": true,
"code": "ok",
"data": { },
"warnings": [],
"retryable": false,
"nextAction": null
}