Terminal MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Terminal MCP Server?

Terminal MCP Server is a Model Context Protocol (MCP) server that allows executing commands on local or remote hosts, providing a powerful interface for AI models and applications to execute system commands.

how to use Terminal MCP Server?

To use Terminal MCP Server, install it via Smithery or manually clone the repository, install dependencies, and start the server using npm commands. You can execute commands locally or remotely via SSH.

key features of Terminal MCP Server?

  • Local and remote command execution
  • Session persistence for reusing terminal environments
  • Custom environment variable support
  • Multiple connection methods including stdio and SSE (Server-Sent Events)

use cases of Terminal MCP Server?

  1. Executing system commands on local machines
  2. Running commands on remote servers via SSH
  3. Maintaining persistent sessions for command execution

FAQ from Terminal MCP Server?

  • Can I execute commands on remote hosts?

Yes! You can execute commands on remote hosts using SSH.

  • How do I maintain a session?

Use the session parameter to maintain the environment for a specified time (default 20 minutes).

  • What are the connection methods available?

You can connect via stdio or SSE for remote connections.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Hellogrowthcrm

2 hours ago
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.

a day ago
Payai X402 Tools

11 hours ago