<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Notes on Aaron Gabbert</title><link>https://gabbert.me/notes/</link><description>Recent content in Notes on Aaron Gabbert</description><generator>Hugo</generator><language>en-US</language><copyright>© Aaron Gabbert</copyright><atom:link href="https://gabbert.me/notes/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Claude Code with n8n MCP triggers</title><link>https://gabbert.me/notes/using-claude-code-with-n8n-mcp-triggers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://gabbert.me/notes/using-claude-code-with-n8n-mcp-triggers/</guid><description>&lt;p&gt;n8n has an &lt;a href="https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/"&gt;MCP Server Trigger Node&lt;/a&gt; that I&amp;rsquo;m using to play around with local MCP in Claude Code. This is just some basic testing/exploration for MCP integration between Claude Code and n8n. If I were going to use this for meaningful work, I’d put a lot more thought into curating responses and prompting via the tool parameters/descriptions!&lt;/p&gt;</description></item></channel></rss>