Vozora
io.vozorav1.0.0Updated Oct 7, 2026
Manage Vozora VPS servers, SSH keys, firewalls, DNS and usage from an AI agent.
Overview
AI-generated overview
Lets an assistant manage Vozora VPS servers, SSH keys, firewalls, DNS records and usage through a remote MCP endpoint.
- What it does
- Vozora exposes a remote MCP endpoint for administering Vozora VPS infrastructure. According to the registry description, an assistant can work with servers, SSH keys, firewalls, DNS and usage data. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Useful when you already run VPS instances on Vozora and want an assistant to handle routine infrastructure tasks such as key, firewall or DNS changes without switching to a control panel. Less relevant if your hosting is elsewhere.
- Requirements
- A remote streamable HTTP endpoint at mcp.vozora.io; no local package or runtime is needed. Authentication is optional: either an Authorization header carrying a scoped Vozora API key as a bearer token, or OAuth sign-in if the header is omitted. A Vozora account is implied.
Before you install
The Authorization header carries a scoped Vozora API key; treat it as a secret and grant only the scope needed. The server can change infrastructure such as firewalls, DNS and SSH keys, so assistant actions may affect live servers. The manifest declares no authentication requirement, so confirm how access is actually controlled before connecting.
Installation
In SourceWeft
- Open Vozora in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"vozora": {
"type": "http",
"url": "https://mcp.vozora.io/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 7, 2026

