Local Mcp Server Tutorial

Created By
7nohea year ago
ローカルMCPサーバー(stdio)を作成するためのチュートリアルです。
Overview

What is Local MCP Server Tutorial?

Local MCP Server Tutorial is a comprehensive guide to creating a local MCP server using Node.js and the Model Context Protocol (MCP).

How to use Local MCP Server Tutorial?

To use this tutorial, follow the step-by-step instructions provided to set up your local MCP server, including project creation, building TypeScript code, and implementing the server.

Key features of Local MCP Server Tutorial?

  • Detailed instructions for setting up a local MCP server.
  • Code examples for building and running the server.
  • Guidance on installing necessary libraries and debugging.
  • Instructions for publishing the MCP server as an npm package.

Use cases of Local MCP Server Tutorial?

  1. Setting up a local development environment for MCP applications.
  2. Learning how to implement resources and tools in an MCP server.
  3. Debugging and testing MCP server functionalities.

FAQ from Local MCP Server Tutorial?

  • What prerequisites are needed to follow this tutorial?

You need Node.js (v22) and a compatible MCP client like Claude Desktop.

  • Is this tutorial suitable for beginners?

Yes! The tutorial provides step-by-step instructions that are easy to follow for beginners.

  • Can I publish my MCP server package?

Yes! The tutorial includes instructions on how to publish your MCP server as an npm package.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
7nohe
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

a day ago