MYASP.NET MCP · BETA
BetaAPI Keys & Authentication
The Beta uses control-panel-issued API keys. OAuth is not used. Send the key as a Bearer credential to the MCP endpoint through your client’s secure environment-variable support.
Permissions
| Scope | Allows | Recommended for |
|---|---|---|
hosting.read | Inventory, status, settings, capacity, logs, and support-ticket reads. | Audits, diagnostics, dashboards, and cautious first-time use. |
hosting.write | Resource creation, updates, credential rotation, and confirmed deletion. Always paired with read access. | Development agents and controlled automation that must make hosting changes. |
Create and manage keys
- Create keys in Account Settings → Hosting API Keys.
- Use a separate key for each developer, machine, or automation environment.
- Choose names that identify the owner and purpose, such as
Codex – Alice laptoporStaging automation. - Revoke a key immediately when a device is lost, a team member leaves, or exposure is suspected.
- Keys are displayed once and cannot be retrieved later. Create a replacement instead.
Request header
HTTP
Authorization: Bearer $MYASP_API_KEYNever expose a key
Do not place API keys in browser-side JavaScript, public repositories, issue reports, support-ticket text, or AI prompts. The MCP client should read the value from a local secret store or environment variable.
Account selection
When one customer account is linked, most tools can omit accountId. If several accounts are linked, call accounts_list and pass one returned opaque accountId. Never infer account ownership from an email address or username.