Gemini API with MCP Tool Integration

Created By
hitechdka year ago
AI agent that retrieves weather data from the MCP server to provide automated forecasts. Ideal for integration into weather-related applications.
Overview

What is the Weather AI Agent?

The Weather AI Agent is an AI-driven tool that retrieves weather data from the MCP server to provide automated forecasts, making it ideal for integration into weather-related applications.

How to use the Weather AI Agent?

To use the Weather AI Agent, clone the repository, set up your environment variables in a .env file, and run the application using the command python main.py.

Key features of the Weather AI Agent?

  • Integration with Google Gemini API for natural language processing.
  • Automated weather data retrieval from the MCP server.
  • Customizable prompts and responses based on user queries.

Use cases of the Weather AI Agent?

  1. Providing real-time weather forecasts for applications.
  2. Automating responses to user inquiries about weather conditions.
  3. Enhancing weather-related services with AI-driven insights.

FAQ from the Weather AI Agent?

  • What are the prerequisites for using the Weather AI Agent?

You need Python 3.7 or higher, a Google Cloud project with the Gemini API enabled, and an MCP environment set up.

  • Is there a license for the Weather AI Agent?

Yes, the project is licensed under the MIT License.

  • Can I customize the behavior of the Weather AI Agent?

Yes, you can modify the prompt and adjust the response handling in the code.

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

2 days ago