<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prompt Management on GAO AI Blog</title><link>https://gao-blog-7a8ba9.gitlab.io/tags/prompt-management/</link><description>Recent content in Prompt Management on GAO AI Blog</description><generator>Hugo -- gohugo.io</generator><language>ja</language><copyright>© ガオ株式会社 All Rights Reserved.</copyright><lastBuildDate>Wed, 10 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://gao-blog-7a8ba9.gitlab.io/tags/prompt-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Deep Dive Comparison: Langfuse MCP Server vs. Dify Langfuse Plugin in Dify</title><link>https://gao-blog-7a8ba9.gitlab.io/posts/2025-12-10-deep-dive-comparison-langfuse-mcp-server-vs-dify-langfuse-plugin-in-dify/</link><pubDate>Wed, 10 Dec 2025 00:00:00 +0000</pubDate><guid>https://gao-blog-7a8ba9.gitlab.io/posts/2025-12-10-deep-dive-comparison-langfuse-mcp-server-vs-dify-langfuse-plugin-in-dify/</guid><description>&lt;h2 class="relative group"&gt;Langfuse MCP Server Arrives as a Tool for Handling Langfuse Prompts in Dify
 &lt;div id="langfuse-mcp-server-arrives-as-a-tool-for-handling-langfuse-prompts-in-dify" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#langfuse-mcp-server-arrives-as-a-tool-for-handling-langfuse-prompts-in-dify" aria-label="アンカー"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;The release of the Langfuse &lt;a href="https://langfuse.com/docs/api-and-data-platform/features/mcp-server#authentication" target="_blank" rel="noopener noreferrer"&gt;MCP Server&lt;/a&gt;
 has opened a new avenue for accessing Langfuse&amp;rsquo;s prompt management capabilities from external tools. Following this release, some may wonder about the role of the &amp;ldquo;Dify Langfuse Plugin&amp;rdquo; developed by our company and which solution is better.&lt;/p&gt;</description></item></channel></rss>