iterm-mcp

Created By
ferrislucasa year ago
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
Overview

what is iterm-mcp?

iterm-mcp is a Model Context Protocol server that allows users to execute commands in their current iTerm session, providing assistance for REPL and CLI tasks.

how to use iterm-mcp?

To use iterm-mcp, ensure iTerm2 is running and install the server via npx. Configure it for Claude Desktop by adding the server config to the appropriate JSON file based on your operating system.

key features of iterm-mcp?

  • Efficient token use for inspecting relevant output.
  • Natural integration with iTerm, allowing interaction with the model.
  • Full terminal control and REPL support.
  • Minimal dependencies for easy installation.

use cases of iterm-mcp?

  1. Automating command-line tasks with AI assistance.
  2. Interacting with REPL environments seamlessly.
  3. Delegating complex terminal operations to the model.

FAQ from iterm-mcp?

  • What are the requirements to use iterm-mcp?

iTerm2 must be running and Node version 18 or greater is required.

  • Is iterm-mcp safe to use?

Users are responsible for monitoring the commands executed, as there are no built-in safety restrictions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ferrislucas
Star
339
Language
TypeScript
License
MIT license
Tags

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.

28 minutes ago