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.
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.
- 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/list` and `prompts/get` methods, for clients that speak them
- Cursor-based pagination when a project holds more prompts than one page
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).