🤖 Model Context Protocol (MCP) Examples

Created By
sur950a year ago
Overview

What is Model Context Protocol (MCP) Examples?

Model Context Protocol (MCP) Examples is a repository containing modular MCP agent servers built using the Model Context Protocol TypeScript SDK. Each subdirectory in src/ is a self-contained MCP server with various tools and prompts for tasks like code analysis and summarization.

How to use MCP Examples?

To use MCP Examples, clone the repository, install the dependencies, and start the MCP server. You can also set up a local .env file for configuration. The server will run at http://localhost:3000/mcp.

Key features of MCP Examples?

  • Modular design with self-contained MCP servers
  • Tools for code analysis and summarization
  • Easy setup and local testing with MCP Inspector

Use cases of MCP Examples?

  1. Analyzing local code repositories for structure and content.
  2. Summarizing code documentation.
  3. Debugging and testing MCP-based servers using MCP Inspector.

FAQ from MCP Examples?

  • What is the purpose of the MCP Inspector?

MCP Inspector is a UI debugger for MCP-based servers that allows for manual testing and debugging.

  • How do I start the MCP server?

You can start the MCP server by running npm run dev after installing the dependencies.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

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