weather-server MCP Server

Created By
uchoa year ago
Overview

what is MCP Weather Server?

MCP Weather Server is a TypeScript-based Model Context Protocol (MCP) server that implements a simple notes system, demonstrating core MCP concepts through resources representing text notes with URIs and metadata.

how to use MCP Weather Server?

To use the MCP Weather Server, install the dependencies, build the server, and configure it with Claude Desktop by adding the server config to the appropriate directory based on your operating system.

key features of MCP Weather Server?

  • Resources for listing and accessing notes via note:// URIs.
  • Tools for creating new text notes with required title and content parameters.
  • Prompts for generating summaries of all stored notes, returning structured prompts for LLM summarization.

use cases of MCP Weather Server?

  1. Creating and managing text notes for various applications.
  2. Summarizing notes for quick reference and review.
  3. Integrating with other applications that support MCP for enhanced note-taking capabilities.

FAQ from MCP Weather Server?

  • What is the purpose of the MCP Weather Server?

The MCP Weather Server serves as a demonstration of the Model Context Protocol, focusing on a simple notes system.

  • How do I install the MCP Weather Server?

You can install it by running npm install after cloning the repository from GitHub.

  • Can I use this server with other applications?

Yes, it can be integrated with applications that support the Model Context Protocol.

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

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago