<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Aspire on René Dekkers</title><link>https://renedekkers.nl/tags/aspire/</link><description>Recent content in Aspire on René Dekkers</description><image><title>René Dekkers</title><url>https://renedekkers.nl/images/og-default.png</url><link>https://renedekkers.nl/images/og-default.png</link></image><generator>Hugo -- 0.155.2</generator><language>en</language><lastBuildDate>Thu, 14 May 2026 12:28:57 +0200</lastBuildDate><atom:link href="https://renedekkers.nl/tags/aspire/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Code and the Aspire MCP server — debugging with runtime data</title><link>https://renedekkers.nl/posts/claude-code-aspire-mcp-server/</link><pubDate>Tue, 28 Apr 2026 11:00:00 +0200</pubDate><guid>https://renedekkers.nl/posts/claude-code-aspire-mcp-server/</guid><description>Where the previous post was about static analysis of the AppHost, this one connects Claude Code to your running Aspire app through the dashboard&amp;#39;s MCP server. Runtime logs, traces, and resource state — directly in your editor.</description></item><item><title>Claude Code and .NET Aspire — distributed apps without the chaos</title><link>https://renedekkers.nl/posts/claude-code-dotnet-aspire/</link><pubDate>Wed, 22 Apr 2026 12:00:00 +0200</pubDate><guid>https://renedekkers.nl/posts/claude-code-dotnet-aspire/</guid><description>Claude Code becomes much more useful when your distributed architecture is visible in code. That&amp;#39;s exactly what .NET Aspire&amp;#39;s AppHost gives it — from understanding the topology to debugging startup failures.</description></item></channel></rss>