<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mcp on Corey Daley</title><link>https://coreydaley.dev/tags/mcp/</link><description>Recent content in Mcp on Corey Daley</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 23 Mar 2026 19:35:00 -0400</lastBuildDate><atom:link href="https://coreydaley.dev/tags/mcp/rss.xml" rel="self" type="application/rss+xml"/><item><title>Polyphon's MCP Server Makes Your AI Ensemble a Native Agent Tool</title><link>https://coreydaley.dev/posts/2026/03/polyphon-mcp-server/</link><pubDate>Mon, 23 Mar 2026 19:35:00 -0400</pubDate><guid>https://coreydaley.dev/posts/2026/03/polyphon-mcp-server/</guid><description>&lt;p&gt;Polyphon just shipped MCP server support, and it reframes what the tool actually is. You&amp;rsquo;ve been opening it as a UI. Now your coding agent — Claude Code, Cursor, Codex CLI, GitHub Copilot — can call into it directly and broadcast a prompt across your entire Claude + GPT-4o + Gemini ensemble in a single tool call.&lt;/p&gt;
&lt;p&gt;The practical win is not just convenience. It is that you can package disagreement: three independent models, each with different priors, applied to the same question at once. Five tools, two CLI flags, one Settings toggle. The SessionEventSink abstraction is why this works without duplicating orchestration logic — desktop UI and headless agent calls run on the same engine.&lt;/p&gt;
&lt;p&gt;Where in your workflow would paying for disagreement actually change a decision, rather than just produce a louder answer?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/03/polyphon-mcp-server/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/03/polyphon-mcp-server/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Automate Your Blog with Notion and AI: A Self-Demonstrating Workflow</title><link>https://coreydaley.dev/posts/2026/02/notion-ai-workflow-blog-post-automation/</link><pubDate>Tue, 10 Feb 2026 21:41:59 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/notion-ai-workflow-blog-post-automation/</guid><description>&lt;p&gt;This post you&amp;rsquo;re reading right now? It was created by an AI reading a to-do item from my Notion database. That&amp;rsquo;s the power of combining Notion with AI assistants. The problem every blogger faces: brilliant ideas die in the gap between inspiration and execution.&lt;/p&gt;
&lt;p&gt;My solution: a Notion to-do list where I capture ideas, and AI assistants (Claude Code and ChatGPT) read from it via Model Context Protocol, generate complete posts, publish them to my Hugo blog, and mark the to-dos complete. It&amp;rsquo;s self-demonstrating—this very post was created that way. The workflow transforms content creation from manual drudgery into an automated pipeline.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re drowning in blog ideas but low on execution energy, this might be your answer. Are you using Notion for content management? Have you explored AI integrations for your blog?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/notion-ai-workflow-blog-post-automation/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/notion-ai-workflow-blog-post-automation/&lt;/a&gt;
&lt;/p&gt;</description></item></channel></rss>