mcpMulti.py

Created By
dmcsvoicesa year ago
A simple chat loop that includes multple mcp servers.
Overview

what is mcpMulti.py?

mcpMulti.py is a Python script that facilitates communication across multiple Model Context Protocol (MCP) servers through a simple chat loop. It includes various server types such as Filesystem MCP Server, CLI MCP Server, and Volatility MCP Server.

how to use mcpMulti.py?

To use mcpMulti.py, ensure you have the OPENAI_API_KEY set in your environment, install the required dependencies using pip install -r requirements.txt, and run the script with python mcpMulti.py.

key features of mcpMulti.py?

  • Supports multiple MCP servers for different functionalities.
  • Filesystem MCP Server for managing file operations.
  • CLI MCP Server for secure command-line interactions.
  • Volatility MCP Server for memory analysis tasks.

use cases of mcpMulti.py?

  1. Managing file operations in a multi-server environment.
  2. Executing terminal commands securely through a command-line interface.
  3. Performing memory analysis using the Volatility framework.

FAQ from mcpMulti.py?

  • What is the purpose of the Filesystem MCP Server?

It manages file operations and directory access for the chat loop.

  • How do I install mcpMulti.py?

You can install it by running pip install -r requirements.txt after cloning the repository.

  • Is there any license for mcpMulti.py?

Yes, it is licensed under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dmcsvoices
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.

8 hours ago