Repository setup required 👋

Created By
Azurea year ago
This repository contains a Remote Model Context Protocol (MCP) Server implemented using Azure Functions, built for enabling tooling support across Azure Native ISV Integrations. It includes MCP tools for Azure-integrated partner services listed under Azure Partner Solutions
Overview

what is azure-native-isv-mcp?

This project is a repository for a Remote Model Context Protocol (MCP) Server implemented using Azure Functions, designed to support tooling for Azure Native ISV Integrations.

how to use azure-native-isv-mcp?

To use this repository, visit the provided GitHub URL to complete the setup and configure access controls for the MCP tools.

key features of azure-native-isv-mcp?

  • Implementation of Remote Model Context Protocol (MCP) Server using Azure Functions.
  • Tools for Azure-integrated partner services.
  • Support for Azure Native ISV Integrations.

use cases of azure-native-isv-mcp?

  1. Enabling tooling support for Azure Native ISV partners.
  2. Facilitating integration of partner services with Azure.
  3. Providing a framework for developing Azure-integrated applications.

FAQ from azure-native-isv-mcp?

  • What is the purpose of this repository?

This repository provides a framework for implementing MCP tools that support Azure Native ISV integrations.

  • Is there any documentation available?

Yes, please refer to the GitHub repository for setup instructions and further documentation.

  • What technologies are used in this project?

The project is built using Azure Functions and follows the Remote Model Context Protocol.

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