MCP Manager Local

Created By
silastorres14a year ago
Server para gerir os servidores de MCP
Overview

what is MCP Manager Local?

MCP Manager Local is a simple web-based manager for starting, stopping, configuring, and viewing logs of MCP (Multi-Capability Protocol) servers, with features for cloning new servers from Git repositories and adding configurations via JSON.

how to use MCP Manager Local?

To use MCP Manager Local, clone the repository from GitHub, install the dependencies, and run the server. Access the web interface at http://localhost:3000 to manage your MCP servers.

key features of MCP Manager Local?

  • Web interface for managing MCP servers
  • Start and stop individual server processes
  • Add configurations manually or via JSON
  • View real-time logs of server output
  • Clone Git repositories containing MCP servers
  • Save server configurations locally in servers.json

use cases of MCP Manager Local?

  1. Managing multiple MCP servers from a single interface.
  2. Cloning and configuring new servers quickly from Git repositories.
  3. Monitoring server logs in real-time for troubleshooting.

FAQ from MCP Manager Local?

  • What are the prerequisites for using MCP Manager Local?

You need Node.js (version 18 or higher) and Git installed on your machine.

  • How do I add a new server configuration?

You can add a new server configuration manually through the web interface or by pasting a JSON object in the designated section.

  • Is there a way to create an executable version of MCP Manager Local?

Yes, you can build an executable using the pkg tool after setting up the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
silastorres14
Star
0
Language
JavaScript
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.

12 hours ago
Voyei

an hour ago