AiR_Orchestrator

Power your agent
Yayıncıdan kurulum. PlugMCP uç noktası değildir.
Host a copy with our keys and logs.
Registry'de henüz paketlenmiş bir sürüm yok. Deponun README dosyasını izleyin.
Uzak URL mi, yoksa makinenizde bir komut mu? İki kurulum arasındaki fark
PlugMCP’de çalıştır
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
BaşlatYayıncıdan

Central backend of AiR platform. Provides HTTP/gRPC APIs, manages users, conversations, AI models and integrations, and coordinates microservices. Features: auth (JWT, TOTP), user/model management, MCP server, gRPC contracts, voice‑call proxy, MinIO/S3, Redis, Swagger/OpenAPI, Prometheus. Secure MasterKey + AES‑GCM
air_orchestrator is the central backend service of the AiR platform. It provides HTTP/gRPC APIs, manages users, conversations, AI models and integrations, and coordinates communication channels and supporting microservices.
pprof profiling.Each user receives an individual MasterKey. It is protected by the user's password and encrypts API keys, channel settings, conversations, Google tokens, CRM configurations, embeddings and file-storage settings. This data can only be decrypted after the user authenticates in the system with their individual password. Even if the database is compromised or leaked, all user data remains inaccessible both to attackers and to the service administration.
System secrets and sensitive app_config values are encrypted with a separate application master key using AES-GCM. The key is loaded from APP_MASTER_KEY_FILE; transactional key rotation is supported through NEW_APP_MASTER_KEY_FILE and APP_CONFIG_REKEY.
air_orchestrator
├── air_db (MariaDB/MySQL)
│ └── users, conversations, configuration and encrypted data
├── air_redis (Redis)
│ └── sessions and user MasterKey cache
├── minio (S3 storage)
│ └── user files
├── envoy
│ └── HTTPS/gRPC-Web gateway and external traffic routing
├── air_tgbot
├── air_tguserbot
├── air_whatsbot
├── air_avito
├── air_operator
├── marusia_crm
├── air_payment
└── air_lead-hunter
build/air-mon.yml
└── cadvisor ── Docker container metrics
build/air-vm.yml
└── victoriametrics ── metrics collection and storage
build/air-vlogs.yml
└── victorialogs ── logs collection and storage
build/air-vector.yml
└── vector ── Docker container log collection into VictoriaLogs
build/air-perses.yml
└── perses ── metrics and logs visualization
.
├── build/ # Dockerfile, Makefile and compose files (dev.yml, prod.yml, air-*.yml)
├── cmd/ # application entry point
├── configs/ # .env and file-based secrets (secrets/ is not committed)
├── doc/ # OpenAPI contract
├── docs/ # generated Swagger files
├── envoy/ # Envoy gateway configuration (dev/prod)
├── internal/ # application code (delivery, usecase, repository, domain)
├── migrations/ # database migrations
└── monitoring/ # VictoriaMetrics, Vector and Perses configuration
Channel, CRM, payment and lead-hunting services communicate with the orchestrator through HTTP/gRPC contracts. The exact set of services depends on the deployment environment and Docker networks air_shared, app_internal and monitoring_shared.
Go 1.25, Gin, gRPC, Protocol Buffers, WebSocket, MariaDB/MySQL, Redis, MinIO/S3, AES-GCM, JWT, TOTP, Google OAuth, MCP Streamable HTTP, Docker, Envoy, Swagger/OpenAPI, VictoriaMetrics, VictoriaLogs, Perses, Vector and cAdvisor.
Create the external networks and prepare secrets:
docker network create air_shared
docker network create app_internal
docker network create monitoring_shared
Then copy configs/secrets.example/ to configs/secrets/ and fill in the values (see secrets example).
For development, from the build/ directory:
make up # infrastructure + dev application
make logs
make down
Equivalent compose invocation (run from build/):
docker compose --env-file ../configs/.env -f dev.yml up -d
Configuration lives in configs/ (.env + secrets/), build files in build/ (Dockerfile, compose files, Makefile). Use build/prod.yml for production. Secrets are mounted from configs/secrets/ and must not be committed.
build/air-vm.yml starts VictoriaMetrics, which collects orchestrator, related-service, container (cAdvisor via build/air-mon.yml) and MinIO metrics every 30 seconds. build/air-vlogs.yml stores logs, build/air-vector.yml collects Docker container logs through docker.sock and ships them to VictoriaLogs. Visualization is provided by Perses (build/air-perses.yml, UI at /perses/, dashboards provisioned from monitoring/perses). All containers use the json-file logging driver with rotation limited to one 10 MB file.
The project is distributed under the MIT license. It permits the free use, copying, modification and distribution of the software provided that the license text and copyright notices are retained.
The full license text is available in the LICENSE file.
Central backend of AiR platform. Provides HTTP/gRPC APIs, manages users, conversations, AI models and integrations, and coordinates microservices. Features: auth (JWT, TOTP), user/model management, MC
Genel bakış
Central backend of AiR platform. Provides HTTP/gRPC APIs, manages users, conversations, AI models and integrations, and coordinates microservices. Features: auth (JWT, TOTP), user/model management, MCP server, gRPC contracts, voice‑call proxy, MinIO/S3, Redis, Swagger/OpenAPI, Prometheus. Secure MasterKey + AES‑GCM
Araçlar
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için stdio yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Air Orchestrator yerel olarak stdio üzerinden çalışır.
Son kontrol: 2026-10-28. Central backend of AiR platform. Provides HTTP/gRPC APIs, manages users, conversations, AI models and integrations, and coordinates microservices. Features: auth (JWT, TOTP), user/model management, MCP server, gRPC contracts, voice‑call proxy, MinIO/S3, Redis, Swagger/OpenAPI, Prometheus. Secure MasterKey + AES‑GCM