What is the architecture?
LibreAgent AI Server for AI Agent Services uses Apache APISIX as the API gateway, etcd for configuration storage, and an AI Service Provider Router to forward traffic to upstream AI services.
@LibreAgent
Basic information
LibreAgent AI Server is an Agentic Accessible Server for API communication with AI Service Providers and AI Services. It supports Google's new Agent 2 Agent (A2A) protocol as well as the MCP protocol. An API gateway is provided in the system for agentic ops.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"a2ahub": {
"command": "docker",
"args": [
"run",
"-d",
"--name",
"mcpo-time",
"--network",
"a2ahub",
"-p",
"8001:8000",
"--rm",
"ghcr.io/open-webui/mcpo:main",
"--host",
"0.0.0.0",
"--port",
"8000",
"--",
"uvx",
"mcp-server-time"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
LibreAgent AI Server for AI Agent Services is a cloud‑native AI gateway built on Apache APISIX that routes traffic to AI agents, including private/public LLMs, MCP servers, and Google A2A agents. It is designed for developers and teams building scalable, secure AI agent infrastructure.
Deploy via Docker using the provided docker-compose.yml (etcd, APISIX, APISIX Dashboard). Quick start: copy env.example to .env, then run docker-compose up -d. Manage routes via the APISIX Admin API (port 9180) or the APISIX Dashboard (port 9000).
mcpo proxyLibreAgent AI Server for AI Agent Services uses Apache APISIX as the API gateway, etcd for configuration storage, and an AI Service Provider Router to forward traffic to upstream AI services.
The gateway supports SSE, WebSockets, and standard HTTP for agent communication.
By default, login with username `admin` and password `admin`. Optionally, you can enable Keycloak for OIDC‑based authentication by uncommenting the relevant blocks in `docker-compose.yml` and `conf.yaml`.
They are local files mounted into Docker containers: `apisix_conf/config.yaml` for APISIX and `apisix_dashboard_conf/conf.yaml` for the Dashboard. The runtime configuration is persisted in etcd.
Yes, it requires Docker and a shared Docker network (named `a2ahub` in the default setup). The provided `docker-compose.yml` launches all components (etcd, APISIX, Dashboard) as containers.
TruVerifAI's Panel Review is the guardian agent for AI's highest-stakes coding decisions: four frontier models argue over an AI coding agent's riskiest designs, diffs, and commits before they execute, with local review g

Extract, search and tag any document — invoices, receipts, contracts, forms, or your own templates. 13 tools, one sign-in (OAuth 2.1) or API key, free FileTag tier, data residency in the EU, US, Israel or Asia.

Build and edit landing pages and websites from your AI assistant, and pull how they are performing.
Model Context Protocol (MCP) server for Hostinger API. If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server: This opens a browser window to authorize via OAuth. Once app
Open-source Node.js FHIR MCP server with SMART Backend Services, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, and terminology lookup.
Comments