Azure Functions ⚡️❤️ MCP Servers

Created By
0GiS0a year ago
Crea tu servidor MCP con Azure Functions ⚡️🧰
Overview

What is MCP Server Azure Function?

MCP Server Azure Function is a project that allows developers to create Model Context Protocol (MCP) servers using Azure Functions, enabling integration with GitHub Copilot Chat.

How to use MCP Server Azure Function?

To use this project, you need to set up an Azure Function and configure it to work with the MCP protocol. You can start by adding the necessary NuGet package and running the provided commands to set up your local environment.

Key features of MCP Server Azure Function?

  • Easy setup of MCP servers using Azure Functions.
  • Integration with GitHub Copilot Chat for enhanced development experience.
  • Local and remote server configuration options.

Use cases of MCP Server Azure Function?

  1. Creating and managing MCP servers for various applications.
  2. Enhancing development workflows with GitHub Copilot Chat.
  3. Testing and deploying Azure Functions in a local environment.

FAQ from MCP Server Azure Function?

  • Can I use this project without Azure?

No, this project is specifically designed to work with Azure Functions.

  • Is there a cost associated with using Azure Functions?

Yes, Azure Functions may incur costs based on usage and the Azure pricing model.

  • How do I deploy my MCP server to Azure?

You can deploy your MCP server using Terraform scripts provided in the repository.

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