powergentic/azd-mcp-ts

Created By
powergentica year ago
An AZD template to deploy a Model Context Protocol (MCP) server written in TypeScript to Azure Container Apps using SSE Transport.
Overview

What is azd-mcp-ts?

azd-mcp-ts is an AZD template designed to deploy a Model Context Protocol (MCP) server written in TypeScript to Azure Container Apps using SSE Transport.

How to use azd-mcp-ts?

To use this template, follow these steps using the Azure Developer CLI:

  1. Log in to Azure Developer CLI with azd auth login.
  2. Initialize the template using azd init --template powergentic/azd-mcp-ts.
  3. Provision Azure infrastructure and deploy the app with azd up.
  4. Verify the MCP server is running by navigating to the /sse URL in your browser.

Key features of azd-mcp-ts?

  • Easy deployment of an MCP server to Azure Container Apps.
  • Built with TypeScript for enhanced development experience.
  • Includes a Dockerfile for building the MCP server app.
  • Integrated logging with Log Analytics and Application Insights.

Use cases of azd-mcp-ts?

  1. Deploying AI solutions that require a Model Context Protocol server.
  2. Customizing the MCP server for specific AI applications.
  3. Streamlining the deployment process for Azure-based applications.

FAQ from azd-mcp-ts?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed to facilitate the context management of AI models.

  • Is there a cost associated with using Azure Container Apps?

Yes, Azure Container Apps may incur costs based on usage and resources provisioned.

  • Can I customize the MCP server after deployment?

Yes, the template allows for customization to fit specific needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
powergentic
Star
1
Language
Bicep
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
Crevio

2 days ago