Snippy

Created By
Azure-Samplesa year ago
🧩 Demo: Build AI-powered MCP Tools for GitHub Copilot using Azure Functions, OpenAI, AI Agents & Cosmos DB. Manages code snippets w/ vector search.
Overview

What is Snippy?

Snippy is an AI-powered code snippet management service built on Azure Functions, designed to manage and analyze code snippets using advanced AI techniques.

How to use Snippy?

To use Snippy, set up the Azure Functions environment, clone the repository, and run the service locally or deploy it to Azure. You can interact with Snippy through HTTP endpoints or Model Context Protocol (MCP) tools in GitHub Copilot.

Key features of Snippy?

  • Save and retrieve code snippets using HTTP/MCP triggers.
  • Generate vector embeddings for snippets using Azure OpenAI.
  • Perform deep research and generate style guides for code snippets.
  • Utilize durable workflows for complex operations.

Use cases of Snippy?

  1. Managing and storing code snippets for easy retrieval.
  2. Analyzing code snippets for best practices and style guides.
  3. Integrating with GitHub Copilot for enhanced coding assistance.

FAQ from Snippy?

  • Can Snippy handle all programming languages?

Yes! Snippy is designed to work with various programming languages supported by Azure Functions.

  • Is Snippy free to use?

Yes! Snippy is open-source and free to use.

  • How does Snippy ensure the security of code snippets?

Snippy utilizes Azure Functions' built-in security features, including authentication and secure storage.

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

a day ago