Getting Started with Remote MCP Servers using Azure Container Apps (Node.js/TypeScript)

Created By
Azure-Samplesa year ago
This is a quick start guide that provides the basic building blocks to set up a remote Model Context Protocol (MCP) server using Azure Container Apps. The MCP server is built using Node.js and TypeScript, and it can be used to run various tools and services in a serverless environment.
Overview

what is mcp-container-ts?

The mcp-container-ts project allows users to host an MCP (Multi-Container Platform) server within a containerized environment.

how to use mcp-container-ts?

To use this project, clone the repository, navigate to the project directory, and follow the installation instructions to set up the server in a container.

key features of mcp-container-ts?

  • Easy setup of an MCP server in a container
  • Supports multiple container configurations
  • Includes a demo application to showcase usage

use cases of mcp-container-ts?

  1. Hosting microservices in a containerized environment.
  2. Simplifying the deployment of applications using MCP.
  3. Testing and development of containerized applications.

FAQ from mcp-container-ts?

  • What is an MCP server?

An MCP server allows for the management and orchestration of multiple containers.

  • Is there a demo available?

Yes! A demo app is included to demonstrate how to use the project.

  • What are the prerequisites for using this project?

You will need a compatible operating system and the necessary libraries installed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Azure-Samples
Star
4
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

an hour ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago