MCP Server with Claude Cursor & Weather API Integration

Created By
onon1999a year ago
mcp-memory-chat / mcp server intregation with claude/Cursor/cmd
Overview

what is MCP Server with Claude Cursor & Weather API Integration?

This project is a custom Minecraft Server (MCP) designed to integrate with Claude Cursor for enhanced interaction through the command line interface (CLI), and it also utilizes a Weather API to provide real-time weather updates in the server.

how to use MCP Server?

To use the MCP Server, follow the setup instructions to install the server, integrate Claude Cursor, and set up the Weather API. Once configured, you can run the server and execute commands via the CLI.

key features of MCP Server?

  • Fully functional Minecraft server setup.
  • Integration with Claude Cursor for CLI commands.
  • Real-time weather updates through the Weather API.

use cases of MCP Server?

  1. Get real-time weather data in Minecraft chat.
  2. Enhance server interaction with custom commands via Claude Cursor.
  3. Provide users with a unique gaming experience by integrating external data.

FAQ from MCP Server?

  • How do I get the Weather API key?

You can create an account on any Weather API provider like OpenWeatherMap and obtain your API key.

  • What should I do if the server crashes?

Ensure that you have the correct version of Java installed and check the server logs for errors.

  • Can I add more commands?

Yes! You can extend the functionality by adding more commands through Claude Cursor integration.

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