dfradehubs/agentgram

代理报

一个MCP端点。一个聊天。每个座席。

所有AI代理都有一个统一的正门——Agentgram在进场时会说REST、A2A和ADK， 并且在离开时会发出干净的AG-UI事件，因此UI无需关心代理的构建方式。

📖 文档与指南

---

为什么

我总是为每个构建的代理生成不同的聊天窗口——一个是针对Kubernetes的 代理、日志和指标——每个协议都有自己的协议。Agentgram 是 我想要的单一前门：一个聊天界面，一个API，每个代理，不管每个代理怎么样 下面有线路。

API是一个多路复用器。它负责认证、权限和会话存储，与每个代理通信 它是原生协议，并将所有内容转换为统一的AG-UI事件流。网页客户端 只需渲染该流——它永远不需要知道答案是否来自 REST 端点，或者 A2A peer 或 Google ADK 应用。

[!提示] 杀手级功能——将所有内容集中在RBAC之后。 将Agentgram指向每一个代理和 公司内的MCP服务器——无论他们使用ADK、A2A还是自定义协议——并对其进行公开

Agentgram

One MCP endpoint. One chat. Every agent.

A single front door for all your AI agents — Agentgram speaks REST, A2A and ADK on the way in, and emits clean AG-UI events on the way out, so the UI never has to care how an agent is built.

📖 Documentation & guides

---

Why

I kept ending up with a different chat window for every agent I built — one for the Kubernetes agent, another for logs, another for metrics — each speaking its own protocol. Agentgram is the single front door I wanted: one chat UI, one API, every agent, regardless of how each one is wired underneath.

The API is a multiplexer. It handles auth, permissions and session storage, talks to each agent in its native protocol, and converts everything to a uniform stream of AG-UI events. The web client just renders that stream — it never needs to know whether an answer came from a REST endpoint, an A2A peer or a Google ADK app.

[!TIP] The killer feature — centralize everything, behind RBAC. Point Agentgram at every agent and MCP server in your company — whether they speak ADK, A2A or a custom protocol — and expose them through one API endpoint and one MCP endpoint. Role-based access control (RBAC) decides exactly who can reach which agent or MCP, so a single integration hands each person precisely the tools they’re entitled to — and nothing else. No more N integrations, N logins, N tools to wire up per client.

Features

• 🏢 Centralize N agents and N MCP servers — register everything your company runs and reach it all through one API endpoint and one MCP endpoint.
• 🛡️ RBAC — fine-grained, per-agent and per-MCP access control by group or user. Each caller only ever sees what they’re allowed to.