Hide MCP Server

MCP server for Hide

Local serverstdioPython

What is the Hide MCP server?

Most AI and media services work still happens through a UI a human drives. Hide MCP server moves it into the conversation instead. MCP server for Hide.

The short version

The server implements two tools adapted from Anthropic's computer-use-demo:

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Tools — The server implements two tools adapted from [Anthropic's computer-use-demo](https://github.com/anthropics/anthropic-quickstarts/tree/main/computer-us
  • Bash — A persistent bash shell with support for common Linux/Python packages, background processes and automatic output truncation
  • Packaging — This will create a standalone executable in the dist/ directory
  • Debugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP

Getting it running

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: UV_PUBLISH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Hide's toolset — Tools, Bash, Packaging and 1 more — is a fair guide to whether it matches your workflow. It is maintained by hide-org; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Hide's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ToolsThe server implements two tools adapted from [Anthropic's computer-use-demo](https://github.com/anthropics/anthropic-quickstarts/tree/main/computer-use-demo/computer_use_demo/tools):
BashA persistent bash shell with support for common Linux/Python packages, background processes and automatic output truncation.
PackagingThis will create a standalone executable in the dist/ directory.
DebuggingSince MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).

How to install the Hide MCP server

"mcpServers": {
    "hide-mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/hide-mcp",
        "run",
        "hide-mcp"
      ]
    }
  }

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
UV_PUBLISH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Hide to Tools.
  • Use Hide to Bash.
  • Use Hide to Packaging.

Frequently asked questions

The server provides two tools: Text Editor (view, edit, create, replace, insert, track history) and Bash (persistent shell with common packages and background processes).