Back to home

Compare

Comparing: HEMA's MCP Chat Exposes the Real Organizational Problem & HEMA 用 MCP 把内部知识装进聊天框 — 这本质是组织问题

AEN
HEMAMCPAmazon Bedrock·

HEMA's MCP Chat Exposes the Real Organizational Problem

This is the daily reality for engineers across HEMA's 750+ stores: looking up how to request an API, or figuring out as a new hire who owns which system, requires hopping between wikis, service catalogs, and IT portals—what they themselves call "portal-hopping." The problem isn't a lack of knowledge; HEMA already had a structured service catalog. The problem is that the "how we actually get things done" part is scattered everywhere, with nobody organizing it.

What this is

As described in a joint AWS-HEMA blog post, the solution: they built HAL, an internal assistant on Amazon Bedrock AgentCore (AWS's enterprise AI Agent hosting platform), consolidated knowledge into one layer, and pushed it via MCP (Model Context Protocol—an open standard that lets LLMs directly call external tools and data sources) into the chat tools and IDEs (including Kiro and Claude) that employees already use. Security is anchored to Microsoft Entra ID; employees don't hold AWS credentials, and permissions inherit from the company's existing identity system.

Industry view

This marks the first time a century-old retailer has deployed MCP in real production and publicly detailed the architecture, since Anthropic open-sourced the protocol in late 2024. Supporters will argue: enterprise AI adoption has long been bottlenecked by "scattered knowledge," and MCP provides a relatively standardized tool-access layer, letting chat tools, IDEs, and Agents pull data directly—avoiding every team reinventing the wheel. AWS bundling Bedrock AgentCore with MCP is a clear bet on this path. Skeptics counter: HEMA itself admits HAL is currently just a read-only knowledge layer—the action layer is next, meaning you can only ask, not do. The MCP ecosystem is still early; the operational cost, security boundaries, and liability for in-house MCP servers remain unanswered. We think the deeper signal is this: the piece repeatedly emphasizes "the knowledge was hard to reach" rather than "the knowledge didn't exist," telling us the real bottleneck is the organization's will to document. AI merely shines a brighter light on an old problem.

Impact on regular people

  • For enterprise IT: the internal knowledge entry point is shifting from "web search" to "ask in chat"—provided the company is willing to spend money and people to organize scattered documents into structured knowledge.
  • For working professionals: new hires will no longer depend on "asking the person next to you," but that also means the implicit value of those human connections is eroding.
  • For consumer markets: consumers won't notice much in the short term; but once HAL upgrades from read-only to actionable, store operations, customer service, and supply chain scheduling could all be rewritten.
BZH
HEMAMCPAmazon Bedrock·

HEMA 用 MCP 把内部知识装进聊天框 — 这本质是组织问题

这是荷兰百年零售商 HEMA 旗下 750 多家门店的工程师长期面对的场景:查个 API 怎么申请、新人要知道找谁负责哪个系统,得在 wikis、服务目录、IT 门户之间反复跳转——他们自己叫它 portal-hopping。问题不是没知识,HEMA 原本就有结构化的服务目录;问题在于"怎么做事"那部分散落各处,没人整理。

这是什么

AWS 与 HEMA 联合发布的博客描述了他们的解法:在 Amazon Bedrock AgentCore(AWS 面向企业的 AI Agent 托管平台)上搭了内部助手 HAL,把知识统一存一层,再通过 MCP(Model Context Protocol,让大模型直接调用外部工具和数据源的协议)推送到员工已经在用的聊天工具和 IDE(包括 Kiro、Claude)。安全锚定在 Microsoft Entra ID,员工端不持有 AWS 凭证,权限沿用企业现有账号体系。

行业怎么看

这是 MCP 自 2024 年底被 Anthropic 开源以来,第一次有百年零售企业把它用在真实生产环境、并公开讲清楚架构。支持者会说:企业 AI 落地长期卡在"知识散落",MCP 给了一个相对标准的工具接入层,让聊天工具、IDE、Agent 都能直接拉数据,避免每个团队重复造轮子;AWS 把 Bedrock AgentCore 与 MCP 打包销售,明显在押注这条路径。怀疑的声音同样存在:HEMA 自己承认目前 HAL 还只是 read-only knowledge layer,下一步才是 action layer——意味着现在只能问、不能做;MCP 生态仍在早期,企业自建 MCP server 的运维成本、安全边界、责任归属都还没成熟答案。更深一层,文章反复强调"the knowledge was hard to reach"而非"the knowledge didn't exist",说明真正的瓶颈是文档化的组织意愿,AI 只是把这个老问题照得更清楚。

对普通人的影响

  • 对企业 IT:内部知识入口正从"网页搜索"转向"聊天框直接问",前提是公司愿意花钱花人把散落文档整理成结构化知识。
  • 对个人职场:未来新人入职不再依赖"问旁边那个人",但也意味着那部分隐性人脉价值在缩水。
  • 对消费市场:短期内消费者几乎感知不到;但当 HAL 从只读升级为可执行,门店运营、客服、供应链调度都可能因此被重写。