MCP - Model Context Protocol

Created By
AdiGo22a year ago
MCP Server using TypeScript and JavaScript made with official MCP docs handling US Weather data having context for two tools - showing weather forecast and weather alerts for US based location. Used Zod for data validation and architectured two folders - src and build , development (ts) and production (js) respectively.
Overview

What is MCP?

MCP, or Model Context Protocol, is an open standard that allows developers to create secure, two-way connections between their data sources and AI-powered tools, specifically designed to handle US weather data.

How to use MCP?

To use MCP, developers can set up an MCP server using TypeScript and JavaScript, following the provided architecture. They can implement protocol handlers and connect their applications to the server for weather forecasts and alerts.

Key features of MCP?

  • Client-server architecture for flexible data handling
  • Support for TypeScript and JavaScript
  • Data validation using Zod
  • Handles weather forecasts and alerts for US locations

Use cases of MCP?

  1. Building AI applications that require real-time weather data.
  2. Integrating weather alerts into existing applications.
  3. Developing tools that utilize AI for weather predictions.

FAQ from MCP?

  • What programming languages does MCP support?

MCP supports TypeScript and JavaScript for server implementation.

  • Can MCP handle data from multiple sources?

Yes, MCP is designed to connect to multiple servers, allowing for diverse data integration.

  • Is there a specific setup required for using MCP?

Developers need to follow the architecture guidelines and set up the necessary directories for TypeScript and compiled JavaScript.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago