MCP Server Example

Created By
ivanbtrujilloa year ago
Basic MCP Server
Overview

what is MCP Server Example?

MCP Server Example is a basic server designed to be consumed by Cursor or other tools, allowing users to integrate various functionalities easily.

how to use MCP Server Example?

To use the MCP Server, modify the index.ts file to add any desired tools, build the project using pnpm run build, and run it with pnpm run start. Then, create a .cursor/mcp.json file in your project with the appropriate configuration.

key features of MCP Server Example?

  • Simple setup for creating an MCP server
  • Easy integration with Cursor and other tools
  • Customizable by modifying the index.ts file

use cases of MCP Server Example?

  1. Integrating weather data retrieval into applications.
  2. Building custom tools for data processing.
  3. Creating chatbots that utilize external APIs for information.

FAQ from MCP Server Example?

  • Can I add my own tools to the MCP Server?

Yes! You can modify the index.ts file to include any tools you want.

  • Is there a specific command to run the server?

Yes, you can run the server using pnpm run start after building it.

  • How do I configure the MCP server?

You need to create a .cursor/mcp.json file with the necessary configuration for your server.

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