Build

Created By
Aaryash-Shakyaa year ago
using typescript sdk to create different mcp server
Overview

what is MCP Servers?

MCP Servers is a project that allows users to create different MCP (Minecraft) servers using a TypeScript SDK.

how to use MCP Servers?

To use MCP Servers, follow these steps:

  1. Install dependencies using yarn install.
  2. Build the project with yarn build.
  3. Make the generated .js files executable and configure them in the MCP configuration file.

key features of MCP Servers?

  • Easy setup with TypeScript SDK.
  • Generates executable JavaScript files for server commands.
  • Customizable server configurations.

use cases of MCP Servers?

  1. Creating custom Minecraft servers for different game modes.
  2. Automating server management tasks.
  3. Integrating with other tools and services for enhanced gameplay.

FAQ from MCP Servers?

  • Can I create multiple servers with MCP Servers?

Yes! You can create as many servers as you need by configuring them in the MCP configuration file.

  • Is there a specific version of TypeScript required?

It is recommended to use the latest version of TypeScript for compatibility.

  • How do I troubleshoot issues with my server?

Check the logs generated by the server for any errors and ensure that the configuration is correct.

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

8 hours ago