Langfuse Prompt Management MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Langfuse Prompt Management MCP Server?

Langfuse Prompt Management MCP Server is a server that allows users to access and manage Langfuse prompts through the Model Context Protocol (MCP).

how to use Langfuse Prompt Management MCP Server?

To use the server, you need to build it using npm, configure it with your Langfuse API keys, and add it to your MCP clients like Claude Desktop or Cursor.

key features of Langfuse Prompt Management MCP Server?

  • Implements MCP Prompts specification for prompt discovery and retrieval.
  • Provides endpoints to list and get specific prompts.
  • Exports tools for compatibility with other MCP clients.

use cases of Langfuse Prompt Management MCP Server?

  1. Managing and retrieving prompts for AI applications.
  2. Integrating prompt management into various MCP clients.
  3. Facilitating prompt discovery for developers.

FAQ from Langfuse Prompt Management MCP Server?

  • What is the MCP Server?

It is a server that implements the Model Context Protocol for managing Langfuse prompts.

  • How do I configure the server?

You need to edit the configuration files of your MCP clients with your Langfuse API keys.

  • Are there any limitations?

Yes, only prompts with a 'production' label are returned, and all arguments are assumed to be optional.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago