tmux-mcp-tools

Created By
PsychArcha year ago
MCP server providing tmux integration tools
Overview

what is tmux-mcp-tools?

tmux-mcp-tools is a Model Context Protocol (MCP) server that provides tools for interacting with tmux sessions, enhancing the user experience with terminal multiplexing.

how to use tmux-mcp-tools?

To use tmux-mcp-tools, you need to set up the MCP server and use the provided commands to interact with tmux sessions.

key features of tmux-mcp-tools?

  • tmux_capture_pane: Capture the content of a tmux pane.
  • tmux_send_command: Send commands to a tmux pane with automatic Enter key.
  • tmux_write_file: Write content to a file using heredoc pattern in a tmux pane.

use cases of tmux-mcp-tools?

  1. Capturing output from long-running processes in tmux.
  2. Automating command execution in tmux sessions.
  3. Writing logs or outputs directly to files from tmux panes.

FAQ from tmux-mcp-tools?

  • What is tmux?

tmux is a terminal multiplexer that allows you to manage multiple terminal sessions from a single window.

  • How do I install tmux-mcp-tools?

Follow the installation instructions provided in the repository.

  • Is tmux-mcp-tools free to use?

Yes! tmux-mcp-tools is open-source and free to use under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PsychArch
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago