get-promptsLABSCO SUMMARY
Your managed prompts, available where you are writing.
It exposes the same thing twice on purpose — as MCP prompts for clients that support the capability, and as tools for the ones that do not — so a prompt kept in Langfuse can be fetched and compiled with variables without leaving the session. Prompt arguments arrive without descriptions and all marked optional, because Langfuse variables carry no specification to pass along.
What it is
A Node server over Langfuse Prompt Management. It implements the MCP prompts specification, and mirrors the same two operations as ordinary tools for clients that do not support prompts.
What you get
- Every prompt in the Langfuse project listed with its arguments
- A named prompt fetched and compiled with the variables you pass
- Langfuse text and chat prompts both transformed into MCP prompt objects
- The native
prompts/listandprompts/getmethods, for clients that speak them - Cursor-based pagination when a project holds more prompts than one page
Requirements
Node.js; clone, npm install, npm run build, then point the client at build/index.js by absolute path. Three environment variables carry the connection: a Langfuse project's public key and its secret key, plus the base URL of the instance you are on (https://cloud.langfuse.com for Langfuse Cloud).
Setup effort
Build from source — git clone https://github.com/langfuse/mcp-server-langfuse.git
USE CASES
01
Using a prompt your team already maintains
Fetch it by name and have it compiled with the variables you pass, instead of copying the text across.
02
Finding out what prompts exist
List them with their arguments; cursor pagination covers projects with more than one page.
03
Working in a client that does not support MCP prompts
The same two operations are exposed as ordinary tools, so nothing depends on the prompt capability.
04
Keeping a multi-message prompt in one place
Langfuse chat prompts come back as MCP prompt objects, so the message structure survives the trip.
2 tools
Listed in project docs. Your client may show a different list.
get-promptBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- LANGFUSE_PUBLIC_KEY in your environment
- LANGFUSE_SECRET_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/langfuse/mcp-server-langfuse.git
cd mcp-server-langfuse
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"langfuse": {
"command": "node",
"args": [
"<YOUR_ABSOLUTE_PATH>/build/index.js"
],
"env": {
"LANGFUSE_PUBLIC_KEY": "<YOUR_LANGFUSE_PUBLIC_KEY>",
"LANGFUSE_SECRET_KEY": "<YOUR_LANGFUSE_SECRET_KEY>",
"LANGFUSE_BASEURL": "https://cloud.langfuse.com"
}
}
}
}
