Virohana Site

Overview

Virohana exposes its public website content as an open, read-only Model Context Protocol (MCP) server. Upstream documentation describes it as the Virohana site connector for asking about Virohana, its services and products, and journal content.

Installation

No local server package is published for this registry entry. Connect to the hosted remote MCP endpoint directly:

{
  "mcpServers": {
    "virohana": {
      "url": "https://mcp.virohanalife.com/mcp"
    }
  }
}

The Virohana connection page also documents an optional terminal/client bridge command:

npx mcp-remote https://mcp.virohanalife.com/mcp

Configuration

Remote endpoint: https://mcp.virohanalife.com/mcp Transport: streamable HTTP. Authentication: open access; no sign-in, API key, or custom header is required for the site content server. Query parameters: none documented. Environment variables: none documented for this hosted remote server.

Claude setup documented upstream: open Claude Settings, go to Connectors, add a custom connector, paste the connector URL, and confirm. Virohana notes that Claude custom connectors require a paid Claude plan. Other MCP-capable clients such as Cursor, VS Code, and Cline can use the URL configuration above.

Capabilities

Documented tools for the site content server are start_here, about_virohana, list_services, service_detail, list_products, product_detail, list_journal, read_post, and search_site.

The server exposes curated content from the Virohana website, including information about Virohana, services, products, and journal posts.

Limitations

The site content server is documented as read-only, open/no-key, and egress-isolated. It serves only curated website content. It is distinct from Virohana's booking MCP endpoint and the OAuth-secured founder portfolio MCP endpoint, which are separate services with different endpoints and access behavior.