MCP SERVER

Unix Socket Server

Chau7's MCP server runs on a local Unix socket. No network exposure, no authentication drama. Fast, private IPC.

The problem

  • Local automation should not require network ports or cloud services just to reach your terminal.
  • Stdio-only integrations make it harder to share a stable control surface across tools.

What Chau7 does about it

  • MCP server listens on a local Unix domain socket under the user's home directory.
  • Socket permissions are restricted to the same user account.
  • Bridge processes can pipe stdio to the socket without exposing a public port.
  • Each client connection gets its own MCP session handler.

What is Unix Socket Server in Chau7?

The Unix Socket Server in Chau7 is the transport layer for Chau7's MCP server. Chau7 creates a Unix domain socket at a well-known path under the user's home directory. AI agents like Claude Code and Cursor connect to this socket directly.

No TCP, no HTTP, no port binding. The operating system enforces that only processes running as the same user can access the socket file, providing authentication without passwords or tokens.

How does Chau7's MCP server communicate with AI agents?

Chau7's MCP server communicates through a Unix domain socket created at a predictable path. When an AI client like Claude Code needs to list tabs, read output, or execute commands, it connects to Chau7's socket file directly.

Unix sockets have lower latency and higher throughput than TCP loopback connections because they skip the entire network stack. For MCP tool calls that happen dozens of times per agent session, this overhead reduction in Chau7 adds up.

How does Chau7's Unix socket server compare to other terminals?

Most terminals do not have an MCP server at all. Terminals that support external control typically use TCP or HTTP, exposing a network port that any process on the machine can connect to.

Chau7's MCP server uses a Unix domain socket exclusively. Chau7's socket provides zero network exposure and filesystem-level permission enforcement. No passwords, no tokens, no TLS certificates to manage. Security is enforced by the operating system's file permission model.

Where is Chau7's socket file located?

Chau7 creates the socket under the user's home directory in a predictable location. The exact path is configured during Chau7's auto-registration into Claude Code, Cursor, Windsurf, and other AI client config files.

MCP clients discover Chau7's socket path automatically through the registered configuration. Developers never need to search for or manually specify the socket path.

What happens if Chau7's socket file is not cleaned up?

Chau7 detects stale socket files on launch and removes them before creating a new one. If Chau7 crashes, the next launch will clean up the stale socket automatically.

The socket is created on Chau7's launch and cleaned up on Chau7's exit. No lingering listeners, no zombie processes, and no manual intervention needed.

Questions this answers

  • What is Unix Socket Server in Chau7 terminal?
  • How does Chau7's unix socket server compare to other terminals?
  • How does Chau7's MCP server communicate with AI agents?
  • Where is the socket file located?
  • What happens if the socket file is not cleaned up?

Frequently asked questions

What is Unix Socket Server in Chau7 terminal?

The Unix Socket Server in Chau7 is the transport layer for Chau7's MCP server. Chau7 creates a Unix domain socket at a well-known path under the user's home directory. AI agents like Claude Code and Cursor connect to this socket directly with no TCP, no HTTP, and no port binding.

How does Chau7's unix socket server compare to other terminals?

Most terminals do not have an MCP server at all. Terminals that support external control typically use TCP or HTTP, exposing a network port. Chau7's MCP server uses a Unix domain socket exclusively, providing zero network exposure and filesystem-level permission enforcement without passwords or tokens.

How does Chau7's MCP server communicate with AI agents?

Chau7's MCP server communicates through a Unix domain socket created at a predictable path. AI agents connect to the socket file directly. The operating system enforces that only processes running as the same user can access the socket. No TCP, no ports, no authentication tokens are needed.

Where is the socket file located?

Chau7 creates the socket under the user's home directory in a predictable location. The exact path is configured during Chau7's auto-registration into Claude Code, Cursor, and other AI client config files, so MCP clients discover the socket path automatically.

What happens if the socket file is not cleaned up?

Chau7 detects stale socket files on launch and removes them before creating a new one. If Chau7 crashes, the next launch will clean up the stale socket automatically. No manual intervention is needed.

Is the Unix socket connection secure?

Yes. Chau7's Unix domain socket is protected by the operating system's file permission model. Only processes running as the same user can connect to Chau7's socket. No network ports are opened, so remote access is impossible by design.