Start with read access
Catalogue, location and status inspection can form a limited initial toolset. A client should be able to learn what is supported before obtaining authority to create, cancel or fund resources.
Separate consequential actions
Server cancellation, reinstall and payment actions require explicit scopes and understandable confirmations. Tool descriptions should state their effect, and the server must enforce authorisation rather than trusting the client to behave.
Handle uncertain outcomes
Return operation identifiers and readable errors. Use idempotency where a retry could create an extra resource or payment. Record the outcome without including secrets in tool responses or logs.
Release information must be real
A launch needs a verified endpoint, authentication instructions, supported protocol version and documented limits. No borrowed endpoint, fake SDK release or download link is supplied here.
Separate a tool description from permission to run it
An MCP server can describe catalogue and management tools, while the authenticated account decides which calls a client may execute. A tool called create_server needs server privileges and a valid order decision. A read_catalogue tool should not require a credential with cancellation or billing authority.
Useful tool groups for an infrastructure agent
The intended design covers reading plans and images, checking orders and operations, managing SSH public keys and observing server state. Creating or cancelling a service and starting a payment are consequential actions that require the appropriate authorisation. Return structured identifiers and clear terminal states rather than prose that a client must guess at.
Transport and authentication must be documented
A future remote endpoint needs HTTPS, a supported transport and an explicit token mechanism. Credentials belong in the approved authentication channel, not in a public configuration example. OAuth registration, protocol versions, downloadable stdio packages and compatibility badges must only be published once KoalaVPS implements and verifies them.
A retry must return to the same operation
An agent can lose its connection after the server accepted a request. Persist an operation or idempotency identifier before retrying a paid action. Re-read status after an uncertain response. Timeouts and a missing message do not prove that the original action failed.
No hosted KoalaVPS MCP endpoint is connected here
This page describes a planned integration. It does not register an agent, install a server package, provide credentials or connect a live management tool. The deployment guides explain how customers may host their own MCP applications on a VPS; those applications are separate from a KoalaVPS control-plane service.
A little more clarity.
Is this page itself an MCP protocol endpoint?
No. It is an explanatory web page. A future machine endpoint must be separately implemented, documented and authenticated.
Does an AI agent receive permission to spend just by connecting?
No. Tool discovery and authentication do not replace the account scope, billing checks or approval rules for the requested action.