Reach your machines
Connect registered devices to your assistant through one MCP interface. Work across Windows and Linux from the tools you already use.
Connect your AI assistants to the machines you choose. Hyrcania brings files, processes, and commands from multiple devices into your workflows, within your configured access.
Keep the conversation and the operational context together, from your development machine to your remote server.
Connect registered devices to your assistant through one MCP interface. Work across Windows and Linux from the tools you already use.
Inspect files, check processes, and run commands on connected devices. Turn a question about your environment into an informed next step.
Control whether remote execution is enabled, restrict filesystem tools to allowed directories, and configure blocked commands.
Connect assistants to your environment with identity, device ownership, local access controls, and self-hosted deployment options.
OAuth/OIDC authentication, scoped permissions, and device ownership checks help determine who can use each device and which tool classes they can access.
CURRENT CAPABILITYEnable remote execution explicitly, restrict filesystem tools to allowed directories, and configure blocked command patterns on the agent.
CURRENT CAPABILITYOptional JFrog Boost integration can filter sensitive tool responses. In required mode, a filtering failure blocks the response; the default auto mode can return it unfiltered if Boost fails.
OPTIONAL INTEGRATIONDeploy Hyrcania in your own environment and connect agents to your server over an approved network path. Agents initiate outbound connections, so target devices do not need inbound ports opened for Hyrcania.
For an air-gapped network, the server, identity provider, and compatible AI client must be reachable inside the isolated environment or through an explicitly approved connection. A fully disconnected device cannot be reached remotely.
Independent native credential masking and command allowlisting are planned improvements. They are not yet presented as available protections.
Allowed directories apply to filesystem tools; they do not confine shell commands. When execution is enabled, commands run with the agent account’s operating-system permissions. Configure that account accordingly.
Explore the security model ↗Keep your assistant in the conversation while it works with the devices you connect.
Check disk usage, inspect service status, and review logs on a connected Linux host.
Explore files on a development workstation and check a build runner from the same assistant.
Inspect processes and configuration on connected machines without switching between separate sessions.
See how a conversation on your phone could reach the devices you connect.
Choose a scenario to watch an illustrative conversation. The examples do not connect to a device.
Illustrative animation · no device connection is made
Start with your own server and devices, then connect a compatible assistant.
Agents let you configure command execution, blocked commands, and allowed directories for filesystem tools. Shell commands run with the agent account’s operating-system permissions. Review your configuration before connecting an environment.
Use these examples with your connected assistant. Device names and available operations depend on your setup.
Check the disk usage on my build runner and identify the largest directories I can access.
Check the status of my web service on the connected server and summarize recent errors.
Inspect the project on my workstation and summarize its structure and build instructions.
Run the Hyrcania agent on the machine you want to work with and register it with your server.
Add the Hyrcania MCP connection to a compatible AI client and authenticate.
Ask your assistant to inspect your environment and carry out tasks within the configured access.
Start with self-hosting today. Explore the product direction for managed cloud and enterprise deployments.
Run the infrastructure yourself and connect your own identity provider.
A simpler way to connect devices, with less infrastructure to maintain.
A deployment path for teams with corporate identity and hosting requirements.
Hyrcania focuses on connecting AI assistants to remote device operations through MCP. The core workflow uses tools for files, processes, commands, and device management.
Hyrcania is designed for MCP-compatible clients, including ChatGPT and OpenCode. Connection and authentication setup depend on the client.
Yes. Self-hosting is a central deployment path, with Authentik used for authentication in the current setup.
These offerings are in product planning. This site does not offer checkout or promise availability or final pricing.
One conversation. Your machines. A clearer path to action.
Open Hyrcania console ↗