OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Multi-Agent Systems

Agent Landing Zone Orchestrator

Agent Landing Zone Orchestrator is an open-source Python orchestration service that coordinates specialized conversational agents using grounded knowledge retrieval, natural-language-to-SQL strategies, and MCP tools. It is built on Azure AI Foundry Agent Service and the Microsoft Agent Framework, and documents strategy options that include direct Azure OpenAI access without Agent Service.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Agent Landing Zone Orchestrator — OpenViST project profile in Multi-Agent Systems.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when building a conversational service that needs orchestration across retrieval, structured-data queries, or MCP tools, and you want to choose among the repository’s documented Azure and Microsoft Agent Framework strategies.

Who it is for

  • Developers building conversational agent services with role-specific agents.
  • Teams connecting knowledge retrieval, structured SQL data, or MCP tools to conversational workflows.
  • Azure builders choosing between Foundry Agent Service and direct Azure OpenAI model access.

Documented uses

  • Coordinate specialized agents for conversational responses grounded in retrieved knowledge.
  • Translate natural-language requests into SQL queries for structured data.
  • Connect an agent workflow to tools exposed by an MCP server.
  • Select among documented orchestration strategies, including a framework option without Agent Service.
Before you choose

Requirements & limits

  • The implementation is a Python service and is published under the MIT license.
  • The five documented strategies differ in their dependencies and workflow: MAF Lite uses direct Azure OpenAI access without Agent Service, while other strategies use Foundry Agent Service or MCP.
  • MCP supports SSE and streamable HTTP; SSE is the default, and the endpoint suffix must match the chosen transport.
  • MCP configuration is provided through Azure App Configuration. The service forwards user context and any configured API key to the MCP endpoint.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Configure the MCP strategy

Set the orchestrator’s MCP transport and endpoint configuration for a trusted MCP server.

Before you start

  • Azure App Configuration access
  • An MCP server endpoint; use HTTPS outside local development
  • For API-key authentication, an API key stored as a Key Vault reference

Steps

  1. Set the MCP strategy and choose sse or streamable_http for MCP_SERVER_TRANSPORT.

  2. Set MCP_APP_ENDPOINT to the MCP server base URL or its matching transport endpoint suffix.

  3. If needed, configure MCP_CLIENT_TIMEOUT as an integer greater than zero and provide MCP_APP_APIKEY through a Key Vault reference.

  4. For SSE, use an endpoint ending in /sse; for streamable HTTP, use /mcp. Ensure the suffix matches the selected transport.

Expected outcome

The orchestrator has configuration for connecting to the selected MCP transport; endpoint suffix conflicts are rejected during strategy initialization.

Guide limitations

  • This covers configuration, not a successful connection or tool invocation.
  • The orchestrator forwards the caller’s user-context header and configured API key to the MCP server on every request; use only a trusted server and restrict network access.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for Agent orchestration

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
Agent Landing Zone OrchestratorCoordinate specialized agents for conversational responses grounded in retrieved knowledge.Cloud, Server
Insurance Agentic AIRoute insurance questions to a life, home or auto specialist.Docker, Self-hosted, Web
AI ChatkitCreate and orchestrate agents with custom behavior logic.Linux, Self-hosted, Server, WebThe repository is public and identified as open source. Its README documents a local development setup with Python and Node-based frontend tooling.
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
11 October 2026
Original website title
Azure/agent-app-orchestrator · Official homepage title · retained in its source language
How we review sourcesSuggest a correction