mcpField
P
powergentic/azd-mcp-ts

powergentic/azd-mcp-ts

Local
github.com/powergenticCloud & Infra4Updated 81w ago

About powergentic/azd-mcp-ts

An Azure Developer CLI template for deploying a TypeScript MCP server to Azure Container Apps. It includes Docker-based build and deployment setup, with SSE transport.

Key features

  1. 01TypeScript MCP server template
  2. 02Azure Container Apps deployment
  3. 03SSE transport
  4. 04Docker image build
  5. 05Azure resources provisioning

Use cases

  1. 01Deploying an MCP server to Azure
  2. 02Starting a customizable TypeScript MCP server

MCP support

The template deploys an MCP server that communicates over SSE transport. It provides a starting point for customizing the server's capabilities.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

powergentic/azd-mcp-ts Awesome Badge

An azd template to deploy a Model Context Protocol (MCP) server written in TypeScript to Azure Container Apps using SSE Transport.

Prerequisites

To deploy this template you will need to have the following installed:

Deployment

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

  1. Log in to Azure Developer CLI. This is only required once per-install.

    azd auth login
    
  2. Initialize this template using azd init:

    azd init --template powergentic/azd-mcp-ts
    
  3. Ensure Docker Engine is running on your machine. This will be needed by azd to build the Docker image for the app prior to deployment to Azure Container Apps.

  4. Use azd up to provision your Azure infrastructure and deploy the web application to Azure.

    azd up
    
  5. Once the template has finished provisioning all resources, and Azure Container Apps has completed deploying the app container (this can take a minute or so after azd up completes to finish), the MCP server will be running.

    Screenshot AZD UP completed successfully

  6. To verify the MCP server is running, navigate your browser to the /sse url for the app within your browser.

    Example URL:

    https://ca-mcp-vnv7lqmg46722.bravebeach-29a82758.eastus2.azurecontainerapps.io/sse
    

    This will open a streaming output within the browser that will look similar to the following:

    Screenshot of /sse endpoint on the MCP server

  7. Congratulations, you now have a simple MCP Server written in TypeScript up and running in Azure! You can now customize this app to build the specific MCP server you need for your AI solution.

Architecture Diagram

Diagram of Azure Resources provisioned with this template

In addition to deploying Azure Resources to host the MCP server, this template includes a DOCKERFILE that builds the MCP server app with TypeScript.

Azure Resources

These are the Azure resources that are deployed with this template:

  • Container Apps Environment - The environment for hosting the Container App
  • Container App - The hosting for the MCP server app
  • Log Analytics and Application Insights - Logging for the Container Apps Environment
  • Container Registry - Used to deploy the custom Docker container for the app

Resource Links

Here are some additional resource links that help explain the topics around building custom MCP Servers in TypeScript and about what MCP and SSE are:

Author

This azd template was written by Chris Pietschmann, founder of Powergentic.ai, Microsoft MVP, HashiCorp Ambassador, and Microsoft Certified Trainer (MCT).

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.