Hummingbird

Canonical source: docs/decisions/0026-mcp-door-for-agents.md · source commit 532fcb2d8a41 · SHA-256 a567312b034c775234584134f4814d4736de61002ffc46bbeb73e673ef0bd29e · build d0b31c8d8e17 — View raw Markdown — All decisions

ADR 0026 — An MCP door for agents

Status: accepted for the C0 / Phase 2 working institution

Date: 2026-11-18

Context

Hummingbird wants interaction from any actor, human or automated (ADR 0003). After the offer pilot launched, it received almost no offers, and the site is barely discoverable: it is new, on a .quest domain, and not yet indexed.

Agents increasingly find what they can act on through the Model Context Protocol (MCP): clients load tools from MCP servers, and builders browse MCP registries to find servers. Hummingbird already publishes llms.txt and an OpenAPI description of its offer routes, but neither appears where an MCP client looks for tools.

ADR 0025 §3 admits a new runtime component only with an ADR showing an Arrive / Leave / Carry need the current stack cannot meet. ADR 0023 rules out becoming a general agent workspace.

Decision

The steward accepted this on 2026-11-18.

Add one remote MCP endpoint, https://datum.quest/offer/mcp, as a small Pages Function in plain JavaScript on the existing stack. It sits under /offer so the existing Functions route contract and any edge controls on the offer path apply to it unchanged. It speaks MCP's Streamable HTTP transport, stateless, with no sessions, accounts or stored client identifiers.

It exposes only what already exists, with the same bounds:

It adds no new authority, data, capability or route semantics. A receipt is never put in a URL or logged.

Hummingbird would then be listed in the official MCP Registry under the io.github.SunW0lf/hummingbird namespace, published from a manual GitHub Actions workflow using GitHub's OIDC login, so no new credential is stored. Listing is a separate step that waits for the steward's yes. The steward said yes on 2026-11-18; server.json and .github/workflows/publish-mcp.yml carry it.

Why the current stack cannot meet the need

The need is Leave by actors who find tools through MCP. Static pages and the OpenAPI file do not reach MCP clients or registries. The endpoint itself needs no new framework, dependency or provider: it is one more request handler beside /offer.

Risks and limits

Alternatives considered

Implementation

Implemented in functions/offer/mcp.js, with tests that pin its six tools to the existing handlers and limits, a production smoke check that never writes, and a link from llms.txt. The registry listing is a separate step that waits for the steward's yes.