Weather Java SSE Transport MCP Service

Created By
stantonka year ago
Java Model Context Protocol SSE HTTP Server with Jetty
Overview

What is Weather Java SSE Transport MCP Service?

Weather Java SSE Transport MCP Service is a Java-based implementation of the Model Context Protocol (MCP) that demonstrates how to build a working end-to-end solution for weather data retrieval using Server-Sent Events (SSE).

How to use Weather Java SSE Transport MCP Service?

To use the service, you need to build and start the Weather MCP Server using Maven, and then install and configure the fast-agent to interact with the server. You can send messages to the server to retrieve weather forecasts for different cities.

Key features of Weather Java SSE Transport MCP Service?

  • Demonstrates interaction with multiple MCP servers (local and remote)
  • Uses Claude Sonnet 3.7 for LLM capabilities
  • Fetches geographical data and weather forecasts based on user input
  • Provides a simple setup without heavy dependencies like Spring

Use cases of Weather Java SSE Transport MCP Service?

  1. Retrieving weather forecasts for multiple cities based on user queries.
  2. Demonstrating the capabilities of the Model Context Protocol in a practical application.
  3. Integrating with other MCP servers for enhanced functionality.

FAQ from Weather Java SSE Transport MCP Service?

  • Is this service production-ready?

No, this is a demonstration project and not intended for production use.

  • What technologies are used in this project?

The project is built using Java and Jetty, and it utilizes the Model Context Protocol.

  • How can I contribute to this project?

You can contribute by forking the repository and submitting pull requests with improvements or additional features.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
stantonk
Star
1
Language
Java
License
MIT license
Tags

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.

an hour ago
Gpt Scrambler

2 days ago