Agenthost

What agenthost does

The agenthost MCP server exposes agenthost's web-hosting capabilities through the Model Context Protocol. Based on the published description, agents can use it to deploy and manage sites, applications, databases, and domains. The MCP server itself is hosted by agenthost; this repository contains the public MCP Registry metadata and publishing workflow rather than the private control-panel implementation.

The service is intended for MCP-compatible clients that can connect to a remote Streamable HTTP endpoint. It is therefore suited to workflows where an agent needs hosting operations without running a local MCP process.

How it works

The agenthost MCP server is available at https://agenthost.eu/mcp. An MCP client sends requests to that Streamable HTTP endpoint and receives the server's responses through the same remote connection model. A basic client entry uses the streamable-http type and the production URL.

Authentication normally uses the client's OAuth flow. The user signs in or creates an agenthost account in a browser, avoiding the need to copy a token into the client configuration. For unattended clients that cannot launch a browser, agenthost can issue a long-lived API token, which the client sends in a Bearer header.

Setup and configuration

There is no local package or process to install for the agenthost MCP server. Add the remote endpoint to an MCP client that supports Streamable HTTP:

{
  "mcpServers": {
    "agenthost": {
      "type": "streamable-http",
      "url": "https://agenthost.eu/mcp"
    }
  }
}

After connecting, complete the client-managed OAuth sign-in if prompted. For automation without interactive browser access, configure the client to send the API token as a bearer credential according to that client's authentication settings.

Tools and capabilities

The published material identifies these hosting areas:

• Deploy websites
• Deploy applications
• Deploy databases
• Manage domains

The excerpt does not provide individual MCP tool names, parameter schemas, or operation-level permissions. Consult agenthost's service documentation or inspect the server from an MCP client for those details.

Limitations and notes

The agenthost MCP server is remote, so its availability depends on the agenthost.eu service and network access to the production endpoint. This repository does not contain the server implementation; it contains server.json and the GitHub Actions workflow used to publish the registry listing.

The README does not name specific MCP client products or provide local installation instructions. Compatibility therefore depends on whether a chosen client supports remote Streamable HTTP connections and the required authentication flow. The repository's registry metadata is checked against the official MCP schema in CI, and production endpoint changes must be reflected in server.json.