CHRIS HAY

IDEAS · SYSTEMS · OBJECTS / LONDON · 2026

THE CONNECTED RECORD

Ask
the work.

Find the question. Follow the work. Return to the source.

Search scope
map memoryLARQLFFN graphoperator knowspredictive localitycontext reconstructingMCPHow many episodes?

1 THREAD · 4 SYSTEMS · 5 NOTEBOOK ENTRIES · 2 QUESTIONS · 241 FILMS · 235 CHAPTERS

Search the authored text, its questions and refusals, and the films around it. Drafts keep their status. Chapters identify a topic and a time; only the 2 indexed transcripts provide spoken passages, and their automatic captions are unreviewed. This edition retrieves sources rather than generating an answer. Explore what is connected ↗

16 RESULTS FOR “MCP

EDITORIAL DRAFT / OBSERVATION · ONGOING · V0.1

MCP-CLI / observation

THE WORK. MCP-CLI brings tool-connected interactions into a command-line interface. The project’s repository is the source for current installation instructions and supported providers, transports and commands.

READ THIS DRAFT

AUTOMATIC CAPTIONS / 0:00

MCP Apps: Rich UI for Any AI Client, No Frontend Required

So over the last year, model context protocol or MCP has gone crazy. There are basically MCP interfaces for everything. Whether it's Slack, Canva, Brave, Outlook, you name it, there is an MCP interface for that. And the reason it's gone crazy is that we finally had a standardized way of calling tools. But a problem with MCP is basically MCP interfaces return text. So you connect with your host, i.e. chat GPT VS Code uh

ORIGINAL SOURCE

AUTOMATIC CAPTIONS / 0:27

MCP Apps: Rich UI for Any AI Client, No Frontend Required

Claude um you call the tool, you get your result back, but it renders it in line as part of the conversation as text. What it didn't have until now is a standardized way of presenting UI interfaces. And that's where MCP apps comes in. It was launched about a month ago and it's the first official extension to model context protocol. And probably the bit that surprised everyone is it was co-authored by both Anthropic and OpenAI building upon the MCP UI

ORIGINAL SOURCE

THE PRACTICE / AUTHOR DESCRIPTION

Chris Hay / A house for ideas, systems and objects

Chris Hay. A house for ideas, systems and objects. Building things to find out how they work. Ideas: Questions, research and the notebook. A place for thinking before the answer. Systems: Models, software, design languages and infrastructure. Giving an idea a structure that can be explored. Objects: What is made: software, interfaces, films and publications. An idea takes a form that can be used, watched or held. Chris Hay explores how intelligent systems are represented, executed, understood and experienced. Research, Engineering, Design, Film form one practice. LARQL: Querying and running learned systems. An investigation into what becomes possible when a model can be addressed. VINDEX3: Exploring how a model is represented, and how that representation relates to its execution. HAUSE: A language for how intelligent systems express themselves: claims, evidence, questions, comparisons and refusals. MCP-CLI / CHUK: Tools for connecting agents, models and the systems they use. Research: The questions, the evidence and the boundary of what has been shown. Notebook: The record before the answer. Thoughts, sketches and questions while they are still taking shape. Film: Another medium for thinking. Experiments, explanations and conversations in public. The record is the catalogue of the practice: stable identities, authorship, dates, source credits and citations. Publish the uncertainty as well as the result. IBM Mixture of Experts is an external production in which Chris is a regular panelist; IBM remains its producer.

ORIGINAL SOURCE