mcp-servers

Created By
MCP-Basea year ago
A collection of MCP servers.
Overview

what is mcp-servers?

mcp-servers is a collection of MCP (Minecraft) servers designed for various gameplay experiences and community interactions.

how to use mcp-servers?

To use mcp-servers, clone the repository from GitHub and follow the setup instructions provided in the documentation to launch your own Minecraft server.

key features of mcp-servers?

  • A variety of server configurations for different gameplay styles.
  • Easy setup and deployment instructions.
  • Community-driven development with contributions from various developers.

use cases of mcp-servers?

  1. Hosting a private Minecraft server for friends.
  2. Creating a public server for community gameplay.
  3. Experimenting with different server configurations for modded Minecraft.

FAQ from mcp-servers?

  • Can I customize the servers?

Yes! Each server configuration can be customized to fit your gameplay preferences.

  • Is there support for modded Minecraft?

Yes! The collection includes configurations for both vanilla and modded Minecraft servers.

  • How do I contribute to mcp-servers?

You can contribute by submitting pull requests on GitHub with your server configurations or improvements.

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