MCP Server

Created By
samnguyen539a year ago
Overview

what is MCP Server?

MCP Server is an initial skeleton for the Multi-Agent Code Planner (MCP) server designed to facilitate the execution of planning commands through a set of defined endpoints.

how to use MCP Server?

To use MCP Server, set up the environment by copying the .env.example to .env, install dependencies, and run the server either locally or using Docker Compose. Verify the health of the server using the health check endpoint.

key features of MCP Server?

  • Health check endpoint to monitor server status
  • Ability to execute planning commands via a dedicated endpoint
  • Supports both local and Docker-based setups

use cases of MCP Server?

  1. Developing multi-agent systems that require planning capabilities.
  2. Integrating with other services that need to execute planning commands.
  3. Testing and prototyping planning algorithms in a controlled environment.

FAQ from MCP Server?

  • What are the prerequisites for running MCP Server?

You need Node.js v14+, npm, and Docker with Docker Compose installed.

  • How do I check if the server is running?

You can verify the server's health by sending a GET request to the /health endpoint.

  • Can I run MCP Server without Docker?

Yes, you can run it locally by installing the necessary dependencies and starting the server.

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

21 hours ago