Camacho Mcp

io.github.sanchiricoPublished by GitHub account sanchiricov1.0.0Updated Oct 24, 2026

Persistent tmux terminal for AI agents — real-time spectating, SSH host-group dispatch.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives an AI assistant a persistent tmux terminal, with real-time spectating and SSH host-group dispatch.

What you can do
  • Give the assistant a persistent tmux terminal session that survives across turns.
  • Watch terminal activity in real time while the assistant works.
  • Dispatch commands to groups of SSH hosts.
  • No individual tools are documented in the supplied listing, so exact operations are unconfirmed.
When to use it
Worth adding when you want an assistant to run and keep shell sessions on your own machine, follow along as it works, or push commands to several SSH hosts at once.
Requirements
Runs as a local process over stdio, installed from the npm package camacho-mcp, so Node.js and npm are needed. tmux must be available on the machine. SSH access and configuration are needed for host-group dispatch. No environment variables, headers or authentication are declared.
Before you install
It gives the assistant a live shell on your machine, so commands can change or delete files and data. SSH dispatch can run commands on remote hosts, including in bulk across a group. Spectating exposes terminal output to the assistant. No credentials are declared, but SSH keys already configured on the machine may be used.

Installation

In SourceWeft

  1. Open Camacho Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.