From cd812a56e5b3f3e2e9ee8ac6c3d70488f534f71b Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Sat, 14 Nov 2026 11:17:34 +0100 Subject: [PATCH 1/6] feat(notes): RSS -> MCP --- src/components/Header.astro | 12 +++++- src/components/NoteNav.astro | 36 ++++++++++++----- src/content/notes/rss-to-mcp.mdx | 67 ++++++++++++++++++++++++++++++++ src/layouts/NoteLayout.astro | 20 ++++++---- src/styles/global.css | 7 +++- 5 files changed, 123 insertions(+), 19 deletions(-) create mode 100644 src/content/notes/rss-to-mcp.mdx diff --git a/src/components/Header.astro b/src/components/Header.astro index ceaf935..6514999 100644 --- a/src/components/Header.astro +++ b/src/components/Header.astro @@ -15,7 +15,7 @@ const { title } = Astro.props; {title === SITE_TITLE && PORTRAIT ? : {title}} ) : ( - ↩ Index + Index )} @@ -25,7 +25,6 @@ const { title } = Astro.props; } a { - text-decoration: none; color: var(--theme-sub-text); &:hover { @@ -36,4 +35,13 @@ const { title } = Astro.props; color: var(--theme-bg); } } + + h1 a { + text-decoration: none; + } + + .back span { + display: inline-block; + margin-inline-end: 1ch; + } diff --git a/src/components/NoteNav.astro b/src/components/NoteNav.astro index b7e7670..e98dda4 100644 --- a/src/components/NoteNav.astro +++ b/src/components/NoteNav.astro @@ -12,14 +12,12 @@ const { prev, next } = Astro.props; @@ -27,7 +25,7 @@ const { prev, next } = Astro.props; diff --git a/src/content/notes/rss-to-mcp.mdx b/src/content/notes/rss-to-mcp.mdx new file mode 100644 index 0000000..473e866 --- /dev/null +++ b/src/content/notes/rss-to-mcp.mdx @@ -0,0 +1,67 @@ +--- +title: RSS → MCP +pubDate: 2026-11-14T10:00:00Z +description: How the two standards can work together +slug: rss-to-mcp +published: true +--- + +RSS made personal sites readable by machines. You subscribe to a feed and get new posts as they come out. + +Agents don't subscribe, though. They scrape your site and retell your work in their own words. + +What if every personal site had its own MCP? Instead of just scraping HTML, an agent could ask the site directly and get an answer in the author's own words. RSS pushes what I published. MCP lets you ask about it. + +### The site answers + +[WebMCP](https://github.com/webmachinelearning/webmcp) is an early proposal for this. A page registers its own tools, and the agent calls them instead of guessing from the DOM. + +```js +await document.modelContext.registerTool({ + name: "about", + description: "Who I am and what this site is", + execute() { + return "Vlad's notes on engineering and life"; + } +}); + +await document.modelContext.registerTool({ + name: "ask", + description: "Ask a question, answered from my notes", + inputSchema: { + type: "object", + properties: { question: { type: "string" } }, + required: ["question"] + }, + execute({ question }) { + return answerFromNotes(question); + } +}); + +await document.modelContext.registerTool({ + name: "subscribe", + description: "Get new notes as they come out", + execute() { + // RSS feed, email newsletter, push notifications, etc. + return "https://esafev.com/rss.xml"; + } +}); +``` + +### The feed points to the tools + +RSS and MCP can point to each other. The `subscribe` tool returns my RSS feed, and the feed itself can list my MCP tools. RSS is already extensible through XML namespaces (that's how podcast feeds added chapters and transcripts). + +```xml + + Vlad Esafev + Who I am and what this site is + Answered from my notes + +``` + +### The tools need one shape + +RSS worked because every feed had the same shape, so any reader could parse any site. WebMCP doesn't have that yet, since every page invents its own tool names. The [IndieWeb](https://indieweb.org/) community already figured out shared conventions with Webmention and microformats. + +Could we agree on a few standard tools, too? diff --git a/src/layouts/NoteLayout.astro b/src/layouts/NoteLayout.astro index 0474f13..c596ff4 100644 --- a/src/layouts/NoteLayout.astro +++ b/src/layouts/NoteLayout.astro @@ -40,6 +40,10 @@ const { margin-block: 1em; } + :global(h2, h3) { + margin-block-start: 2em; + } + :global(h2) { font-size: 1.3em; } @@ -70,8 +74,8 @@ const { :global(code) { padding: 0.2rem 0.33rem; margin-inline: -0.125em; - border-radius: 3px; + font-family: inherit; font-size: 0.85em; overflow-wrap: anywhere; @@ -79,19 +83,21 @@ const { } :global(pre) { - --padding-inline: 2rem; - padding: 1rem var(--padding-inline); + --padding-inline: 1.25rem; + margin-block: 1.5em; + padding: 1.25rem var(--padding-inline); padding-inline-end: calc(var(--padding-inline) * 2); overflow: auto hidden; - @media (width >= 37.75em) { - --padding-inline: 1.25rem; - border-radius: 8px; - } + font-family: inherit; } :global(pre > code) { all: unset; + + @media (width <= 480px) { + font-size: 0.9em; + } } } diff --git a/src/styles/global.css b/src/styles/global.css index 10cfa80..a2050c5 100644 --- a/src/styles/global.css +++ b/src/styles/global.css @@ -41,6 +41,11 @@ background-color: light-dark(var(--color-sky-medium), var(--color-klein-light)); } +code::selection, +code ::selection { + background-color: var(--theme-bg); +} + * { box-sizing: border-box; margin: 0; @@ -67,7 +72,7 @@ body { @media (width <= 480px) { body { max-width: 100%; - padding: 1em; + padding: 3em 1em 1em; } } From de346034087c0887133a7aede892e4f72e98acbe Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Sat, 14 Nov 2026 11:18:36 +0100 Subject: [PATCH 2/6] fix(notes): keep code font size on mobile --- src/layouts/NoteLayout.astro | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/layouts/NoteLayout.astro b/src/layouts/NoteLayout.astro index c596ff4..7581c9f 100644 --- a/src/layouts/NoteLayout.astro +++ b/src/layouts/NoteLayout.astro @@ -94,10 +94,6 @@ const { :global(pre > code) { all: unset; - - @media (width <= 480px) { - font-size: 0.9em; - } } } From b7e4ad3166f0ed2461a384329f355ad084d612a7 Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Sat, 14 Nov 2026 11:19:01 +0100 Subject: [PATCH 3/6] fix(notes): reduce code padding on mobile --- src/layouts/NoteLayout.astro | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/layouts/NoteLayout.astro b/src/layouts/NoteLayout.astro index 7581c9f..2214d01 100644 --- a/src/layouts/NoteLayout.astro +++ b/src/layouts/NoteLayout.astro @@ -90,6 +90,11 @@ const { overflow: auto hidden; font-family: inherit; + + @media (width <= 480px) { + --padding-inline: 1em; + padding-block: 1em; + } } :global(pre > code) { From 1349bbd47ed2acecef212e71a0c58eb8f443839f Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Sat, 14 Nov 2026 11:25:50 +0100 Subject: [PATCH 4/6] fix(notes): sharpen RSS -> MCP text --- src/content/notes/rss-to-mcp.mdx | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/content/notes/rss-to-mcp.mdx b/src/content/notes/rss-to-mcp.mdx index 473e866..74edbab 100644 --- a/src/content/notes/rss-to-mcp.mdx +++ b/src/content/notes/rss-to-mcp.mdx @@ -6,11 +6,9 @@ slug: rss-to-mcp published: true --- -RSS made personal sites readable by machines. You subscribe to a feed and get new posts as they come out. +RSS answers one question: what's new? Agents ask other questions, so they scrape your pages and retell your work in their own words. -Agents don't subscribe, though. They scrape your site and retell your work in their own words. - -What if every personal site had its own MCP? Instead of just scraping HTML, an agent could ask the site directly and get an answer in the author's own words. RSS pushes what I published. MCP lets you ask about it. +What if every personal site had its own MCP? Instead of just scraping HTML, an agent could ask the site directly and get back what the author actually wrote. RSS pushes what I published. MCP lets you ask about it. ### The site answers @@ -62,6 +60,6 @@ RSS and MCP can point to each other. The `subscribe` tool returns my RSS feed, a ### The tools need one shape -RSS worked because every feed had the same shape, so any reader could parse any site. WebMCP doesn't have that yet, since every page invents its own tool names. The [IndieWeb](https://indieweb.org/) community already figured out shared conventions with Webmention and microformats. +RSS worked because every feed had the same shape, so any reader could parse any site. An agent can read any tool's description and figure it out - a feed reader can't. If `ask` meant the same thing on every site, your reader could show an "Ask" box for every blog you follow. The [IndieWeb](https://indieweb.org/) community already figured out shared conventions with Webmention and microformats. Could we agree on a few standard tools, too? From 2be4549dba3ee886b68b80214bba930a01ab6f56 Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Sat, 14 Nov 2026 11:38:33 +0100 Subject: [PATCH 5/6] fix(notes): shape -> structure --- src/content/notes/rss-to-mcp.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/content/notes/rss-to-mcp.mdx b/src/content/notes/rss-to-mcp.mdx index 74edbab..6bf2a7c 100644 --- a/src/content/notes/rss-to-mcp.mdx +++ b/src/content/notes/rss-to-mcp.mdx @@ -41,7 +41,7 @@ await document.modelContext.registerTool({ description: "Get new notes as they come out", execute() { // RSS feed, email newsletter, push notifications, etc. - return "https://esafev.com/rss.xml"; + return "[https://esafev.com/rss.xml](https://esafev.com/rss.xml)"; } }); ``` @@ -51,15 +51,15 @@ await document.modelContext.registerTool({ RSS and MCP can point to each other. The `subscribe` tool returns my RSS feed, and the feed itself can list my MCP tools. RSS is already extensible through XML namespaces (that's how podcast feeds added chapters and transcripts). ```xml - + Vlad Esafev Who I am and what this site is - Answered from my notes + Ask a question, answered from my notes ``` -### The tools need one shape +### The tools need one structure -RSS worked because every feed had the same shape, so any reader could parse any site. An agent can read any tool's description and figure it out - a feed reader can't. If `ask` meant the same thing on every site, your reader could show an "Ask" box for every blog you follow. The [IndieWeb](https://indieweb.org/) community already figured out shared conventions with Webmention and microformats. +RSS worked because every feed had the same structure, so any reader could parse any site. An agent can read any tool's description and figure it out, but a feed reader can't. If `ask` meant the same thing on every site, your reader could show an "Ask" box for every blog you follow. The [IndieWeb](https://indieweb.org/) community already figured out shared conventions with Webmention and microformats. -Could we agree on a few standard tools, too? +Could we agree on a few standard tools, too? \ No newline at end of file From 2762769bdc40ff9b2af3b845857f54a82baacad3 Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Sat, 14 Nov 2026 11:43:18 +0100 Subject: [PATCH 6/6] fix(notes): restructure standard section --- src/content/notes/rss-to-mcp.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/notes/rss-to-mcp.mdx b/src/content/notes/rss-to-mcp.mdx index 6bf2a7c..d6a6851 100644 --- a/src/content/notes/rss-to-mcp.mdx +++ b/src/content/notes/rss-to-mcp.mdx @@ -10,7 +10,7 @@ RSS answers one question: what's new? Agents ask other questions, so they scrape What if every personal site had its own MCP? Instead of just scraping HTML, an agent could ask the site directly and get back what the author actually wrote. RSS pushes what I published. MCP lets you ask about it. -### The site answers +### The page [WebMCP](https://github.com/webmachinelearning/webmcp) is an early proposal for this. A page registers its own tools, and the agent calls them instead of guessing from the DOM. @@ -46,7 +46,7 @@ await document.modelContext.registerTool({ }); ``` -### The feed points to the tools +### The feed RSS and MCP can point to each other. The `subscribe` tool returns my RSS feed, and the feed itself can list my MCP tools. RSS is already extensible through XML namespaces (that's how podcast feeds added chapters and transcripts). @@ -58,8 +58,8 @@ RSS and MCP can point to each other. The `subscribe` tool returns my RSS feed, a ``` -### The tools need one structure +### The standard -RSS worked because every feed had the same structure, so any reader could parse any site. An agent can read any tool's description and figure it out, but a feed reader can't. If `ask` meant the same thing on every site, your reader could show an "Ask" box for every blog you follow. The [IndieWeb](https://indieweb.org/) community already figured out shared conventions with Webmention and microformats. +RSS worked because every feed had the same structure, so one reader could follow any site. Agents don't strictly need that, since they can figure out any tool from its description. But feed readers do. If `ask` meant the same thing everywhere, your reader could add an "Ask" box to every blog you follow. -Could we agree on a few standard tools, too? \ No newline at end of file +The [IndieWeb](https://indieweb.org/) already agreed on Webmention and microformats. Could we agree on a few standard tools, too?