Azure Container Apps remote MCP server example

Created By
KRVaghania year ago
Overview

What is Azure-MCP-Server?

Azure-MCP-Server is a FastAPI-based Model Context Protocol (MCP) server designed for Azure Container Apps, providing weather-related tools such as alerts and forecasts through a secure API-key-protected Server-Sent Events (SSE) interface.

How to use Azure-MCP-Server?

To use Azure-MCP-Server, clone the repository, set up the virtual environment, install dependencies, set your API key, and run the server. A sample Python client is included for command-line interaction.

Key features of Azure-MCP-Server?

  • Provides weather alerts and forecasts via SSE.
  • Secure API key authentication.
  • Integration with MCP-compatible clients like Visual Studio Code.

Use cases of Azure-MCP-Server?

  1. Real-time weather alerts for specific US states.
  2. Weather forecasts based on geographic coordinates.
  3. Integration with custom scripts for automated weather data retrieval.

FAQ from Azure-MCP-Server?

  • What programming language is used?

The server is built using Python 3.11 or later.

  • How do I deploy it to Azure?

Use the Azure CLI command provided in the documentation to deploy the server to Azure Container Apps.

  • What should I do if I encounter errors?

Check the troubleshooting section in the documentation for common issues and solutions.

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