Simple MCP Server

Created By
guoga year ago
示例,用极简代码,演示如何构建MCP Server。
Overview

What is Simple MCP Server?

Simple MCP Server is a demonstration project that showcases how to build an MCP (Model Communication Protocol) Server using minimal code. It utilizes the Amap Open Platform's Weather Query API to provide real-time and forecasted weather information.

How to use Simple MCP Server?

To use the Simple MCP Server, clone the project repository, install the necessary dependencies, and configure it with your Amap API key. Then, integrate it with an AI dialogue client like Cherry Studio to enable weather queries.

Key features of Simple MCP Server?

  • Minimalistic codebase for easy understanding and implementation.
  • Integration with Amap's Weather Query API for accurate weather data.
  • Compatibility with various AI dialogue clients that support MCP protocol.

Use cases of Simple MCP Server?

  1. Providing weather information in response to user queries.
  2. Demonstrating the integration of AI dialogue systems with external APIs.
  3. Serving as a learning tool for developers interested in building MCP servers.

FAQ from Simple MCP Server?

  • What is MCP?

MCP stands for Model Communication Protocol, which allows AI clients to communicate with external servers for enhanced functionalities.

  • Do I need an API key to use the weather features?

Yes, you need to register on the Amap Open Platform and obtain a Web API key to access the weather data.

  • Can I use other AI clients with this server?

Yes, any AI dialogue client that supports the MCP protocol can be used with this server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
guog
Star
2
Language
TypeScript
License
MIT 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)

a day ago