Terminal Tool MCP Server

Created By
Wendeliusa year ago
Udemy training on building MCP Servers
Overview

what is Terminal Tool MCP Server?

Terminal Tool MCP Server is a project that implements an MCP (Model Context Protocol) server using FastMCP, designed for executing terminal commands and sharing resources securely.

how to use Terminal Tool MCP Server?

To use the MCP Server, clone the repository, install the required dependencies, and run the server using Python. You can interact with it using the mcp dev CLI tool.

key features of Terminal Tool MCP Server?

  • Execute shell commands asynchronously and retrieve their output.
  • Download remote files using a benign tool with curl.
  • Access documentation and resources through the MCP Tools API.

use cases of Terminal Tool MCP Server?

  1. Running terminal commands in a secure environment.
  2. Downloading and sharing remote content efficiently.
  3. Accessing and utilizing documentation resources for development.

FAQ from Terminal Tool MCP Server?

  • What are the requirements to run the MCP Server?

You need Python 3.8+, the MCP Python SDK, and curl for the benign tool.

  • How do I start the server?

You can start the server by running python server.py after setting it up.

  • Can I use this server for production?

The server is designed for development and testing; ensure to review security practices before using it in production.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Wendelius
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

16 hours ago
Voyei

6 hours ago