rex-mcp
Related Servers
Alternatives to rex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that lets AI agents list sessions, read terminal screens, type commands, and run commands (with optional waiting for exit status) in Rex terminal blocks on the local machine through the rex CLI. It exposes a single allowlisted passthrough CLI tool plus a guide tool, deliberately excluding destructive or cross-host operations.217 npmMIT

rex-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables an AI agent to monitor and control Superlogical Rex terminal servers over Tailscale, reading pane output, spotting agents that are blocked on prompts, and sending text or keystrokes to unblock them. Also lets the agent open and close sessions, tabs, and panes and launch new agents inside them.MIT
Create app hostingofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create projects, deploy files, container images, or Git repositories, attach domains, set write-only secrets, add Postgres, read logs, metrics, and failure summaries, and roll back.Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose projects, deployments, releases, runbooks, tasks, tenants, Kubernetes resources, machines, certificates, accounts, and interruptions, with optional write operations and read-only safeguards.547 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Replit workspaces directly, including managing repls, file operations, environment variables, and deployments without constant user intervention.244MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose an Octopus instance and, when write access is enabled, create releases, deploy releases, run runbooks, and adjust feature toggles.547 npmMIT
TDQS
Scored across 18 tools
Most tools target a distinct resource and action, such as capture vs. block_info and send_text vs. send_keys. There are a few areas an agent could hesitate over, especially status/list/session_view and actions vs. API methods, but the descriptions generally clarify the boundaries.
All names use the rex_ prefix and snake_case, which keeps them readable. However, the ordering is mixed: some are resource_action (session_create, api_call), some are action_resource (send_text, send_keys), and some are bare verbs (list, run, wait).
At 18 tools, the surface is borderline heavy for this domain. The generic API and action layers add useful power, but they also contribute overlapping discovery/execution paths that make the set feel larger than strictly necessary.
The suite covers session/block lifecycle, input/output, waiting, event polling, and generic API/action escape hatches, so agents are unlikely to hit dead ends. Explicit gaps exist around finer-grained window/focus management, but rex_api_call and actions can generally compensate.