Port followed its framing piece with a harder one about what context engineering actually takes at scale, and it opens with a line that will annoy anyone currently maintaining a folder of markdown for their agents: “files don’t scale. Databases do.” The argument is a taxonomy of the three approaches teams reach for first, each with a named failure. An MCP server gives an agent reach, but every relationship between the things it can reach still has to be discovered at runtime — “every structural relationship your agent needs still requires reasoning.” RAG retrieves by vector similarity, which finds text that looks related rather than systems that are related. A file-system approach — markdown and JSON in a repository — works for five services and falls over at five hundred, which they put at roughly five thousand files. Their motivating cost is an agent burning 100,000 tokens on a simple task because it had to reconstruct the org chart of a codebase before doing anything.
The proposed answer is a relational graph with typed nodes and explicit edges, and the post is candid that this is infrastructure rather than a prompt technique: a sync layer that keeps it current, auto-discovery that finds services and infers relationships nobody declared, skills attached to specific nodes, and event tracking so an agent’s decisions become part of the record. The headline figures — 40% better agent accuracy and 70% fewer tokens than MCP and RAG alone — are Port’s own measurements of Port’s own graph, and should be read as a vendor’s direction rather than a benchmark. The sentence that survives without them is the architectural one: “one shared layer, many consumers.”
Monday’s post on Port walked the catalog’s nouns — blueprints, entities, scorecards. This one is about the pipes, and the Port record has those too. The Integrations API is the sync layer behind the 70-plus native integrations the post counts; the Webhooks API is how anything not covered by an integration pushes change in; the Workflows API is the multi-step orchestration the context feeds; the Teams and Users API is the ownership edge half of these relationships depend on; and the Port REST API is the query door for any consumer that is not Port’s own agent.
The scores have not moved since Monday — 31.3, thin, contract quality 0.0, Agent Readiness 19.8, agent-aware — so the measurement worth adding is a different one. This post names Port’s MCP server and its skills as parts of the shipping product. The catalog still reads both mcp_server and agent_skills as dark, and nothing in Port’s registered record points at either. That matters more for Port than for most, because the post’s own thesis is that an agent should not have to reason its way to a relationship that could have been declared. A provider arguing for explicit edges over runtime discovery has left the edge between itself and its agent surfaces for a crawler to discover.