langfuse-mcp-extended
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@langfuse-mcp-extendedlist the last 10 traces from today"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Langfuse MCP Server (Extended)
A comprehensive Model Context Protocol (MCP) server for Langfuse, providing AI assistants with full access to traces, observations, scores, datasets, and sessions.
Prompt Management: This server focuses on observability data. For prompt management, Langfuse provides a built-in MCP server (GitHub). We're working on integrating both - see Contributing.
Features
22 tools for complete Langfuse observability access
Traces: List, get, and delete traces with filtering and pagination
Observations: Query generations, spans, and events with usage metrics
Scores: Full CRUD operations for evaluation scores (numeric, categorical, boolean)
Score Configs: Manage score configuration templates
Datasets: Complete dataset management including items and evaluation runs
Sessions: Access session data with associated traces
Cloud & Self-hosted: Works with Langfuse Cloud (US/EU) and self-hosted instances
Quick Start
One-liner Installation (Claude Code)
claude mcp add langfuse -e LANGFUSE_PUBLIC_KEY=pk-lf-xxx -e LANGFUSE_SECRET_KEY=sk-lf-xxx -- npx -y langfuse-mcp-extendedFor EU Cloud or self-hosted, add the base URL:
claude mcp add langfuse -e LANGFUSE_PUBLIC_KEY=pk-lf-xxx -e LANGFUSE_SECRET_KEY=sk-lf-xxx -e LANGFUSE_BASE_URL=https://eu.cloud.langfuse.com -- npx -y langfuse-mcp-extendedInstallation by Client
Add to your Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"langfuse": {
"command": "npx",
"args": ["-y", "langfuse-mcp-extended"],
"env": {
"LANGFUSE_PUBLIC_KEY": "pk-lf-...",
"LANGFUSE_SECRET_KEY": "sk-lf-..."
}
}
}
}For EU Cloud or self-hosted, add LANGFUSE_BASE_URL:
{
"mcpServers": {
"langfuse": {
"command": "npx",
"args": ["-y", "langfuse-mcp-extended"],
"env": {
"LANGFUSE_PUBLIC_KEY": "pk-lf-...",
"LANGFUSE_SECRET_KEY": "sk-lf-...",
"LANGFUSE_BASE_URL": "https://eu.cloud.langfuse.com"
}
}
}
}Option 1: One-liner with environment variables
claude mcp add langfuse -e LANGFUSE_PUBLIC_KEY=pk-lf-xxx -e LANGFUSE_SECRET_KEY=sk-lf-xxx -- npx -y langfuse-mcp-extendedOption 2: Add to project's .mcp.json
{
"mcpServers": {
"langfuse": {
"command": "npx",
"args": ["-y", "langfuse-mcp-extended"],
"env": {
"LANGFUSE_PUBLIC_KEY": "pk-lf-...",
"LANGFUSE_SECRET_KEY": "sk-lf-..."
}
}
}
}Option 3: Use shell environment variables
claude mcp add langfuse -- npx -y langfuse-mcp-extendedThen set in your shell profile (.bashrc, .zshrc, etc.):
export LANGFUSE_PUBLIC_KEY="pk-lf-..."
export LANGFUSE_SECRET_KEY="sk-lf-..."Add to your Cursor MCP configuration:
Project-specific:
.cursor/mcp.jsonin your project directoryGlobal:
~/.cursor/mcp.jsonin your home directory
{
"mcpServers": {
"langfuse": {
"command": "npx",
"args": ["-y", "langfuse-mcp-extended"],
"env": {
"LANGFUSE_PUBLIC_KEY": "pk-lf-...",
"LANGFUSE_SECRET_KEY": "sk-lf-..."
}
}
}
}Or add via UI: File → Preferences → Cursor Settings → MCP
Add to .vscode/mcp.json in your workspace:
{
"mcpServers": {
"langfuse": {
"command": "npx",
"args": ["-y", "langfuse-mcp-extended"],
"env": {
"LANGFUSE_PUBLIC_KEY": "pk-lf-...",
"LANGFUSE_SECRET_KEY": "sk-lf-..."
}
}
}
}npm install -g langfuse-mcp-extendedThen use langfuse-mcp-extended as the command instead of npx -y langfuse-mcp-extended.
Configuration
Required Environment Variables
Variable | Description |
| Your Langfuse public key ( |
| Your Langfuse secret key ( |
Optional Environment Variables
Variable | Default | Description |
|
| Langfuse instance URL |
|
| Logging level: |
Langfuse Instance URLs
Instance | URL |
US Cloud |
|
EU Cloud |
|
Self-hosted | Your instance URL (e.g., |
API Reference
Pagination
All list operations use page-based pagination with a default limit of 10 items per page:
page(number, optional): Page number, 1-indexed. Default: 1limit(number, optional): Items per page, max 100. Default: 10
Response Size Control
Get operations (getTrace, getSession, getObservation) support an includeIO parameter:
includeIO(boolean, optional): Include input/output fields. Default:false
When includeIO is false (default), large input and output fields are stripped from responses to prevent exceeding LLM context limits. Set to true when you need the full payload.
listTraces
List traces with filtering and pagination.
Inputs:
page(number, optional): Page numberlimit(number, optional): Items per pagename(string, optional): Filter by trace nameuserId(string, optional): Filter by user IDsessionId(string, optional): Filter by session IDtags(string[], optional): Filter by tags (AND logic)fromTimestamp(string, optional): Start of time range (ISO 8601)toTimestamp(string, optional): End of time range (ISO 8601)environment(string, optional): Filter by environmentorderBy(string, optional): Sort bytimestamp,latency, ortotalCost
getTrace
Get a specific trace with full details.
Inputs:
traceId(string, required): The trace IDincludeIO(boolean, optional): Include input/output fields. Default:false
Returns: Trace with observations and scores.
deleteTrace
Delete a trace.
Inputs:
traceId(string, required): The trace ID to delete
listObservations
List observations (generations, spans, events) with cursor-based pagination.
Inputs:
cursor(string, optional): Pagination cursorlimit(number, optional): Items per pagetraceId(string, optional): Filter by trace IDname(string, optional): Filter by observation nametype(string, optional): Filter by type:GENERATION,SPAN,EVENTparentObservationId(string, optional): Filter by parentfromStartTime(string, optional): Start of time range (ISO 8601)toStartTime(string, optional): End of time range (ISO 8601)userId(string, optional): Filter by user IDversion(string, optional): Filter by version
getObservation
Get a specific observation with all details.
Inputs:
observationId(string, required): The observation IDincludeIO(boolean, optional): Include input/output fields. Default:false
Returns: Observation with usage, costs, and timing.
createScore
Create a score for a trace or observation.
Inputs:
traceId(string, required): ID of the trace to scorename(string, required): Score name (e.g.,accuracy,relevance)value(number | string, required): Score valueobservationId(string, optional): ID of specific observation to scoredataType(string, optional):NUMERIC,CATEGORICAL, orBOOLEANcomment(string, optional): Explanation of the scoreconfigId(string, optional): Score config ID for validationid(string, optional): Custom ID for idempotency
listScores
List scores with filtering.
Inputs:
page,limit(pagination)traceId(string, optional): Filter by trace IDobservationId(string, optional): Filter by observation IDname(string, optional): Filter by score namesource(string, optional): Filter by source:API,ANNOTATION,EVALdataType(string, optional): Filter by data typeconfigId(string, optional): Filter by config IDfromTimestamp,toTimestamp(string, optional): Time rangeuserId(string, optional): Filter by user IDoperator(string, optional): Comparison operator:<,>,<=,>=,!=,=value(number, optional): Value to compare (requires operator)
getScore
Get a specific score.
Inputs:
scoreId(string, required): The score ID
deleteScore
Delete a score.
Inputs:
scoreId(string, required): The score ID to delete
createScoreConfig
Create a score configuration template.
Inputs:
name(string, required): Unique config namedataType(string, required):NUMERIC,CATEGORICAL, orBOOLEANminValue(number, optional): Minimum value (NUMERIC only)maxValue(number, optional): Maximum value (NUMERIC only)categories(array, optional): Category definitions (CATEGORICAL only)description(string, optional): Description
listScoreConfigs
List all score configurations.
Inputs:
page,limit(pagination)
getScoreConfig
Get a specific score configuration.
Inputs:
configId(string, required): The config ID
createDataset
Create a new dataset.
Inputs:
name(string, required): Dataset namedescription(string, optional): Descriptionmetadata(object, optional): Additional metadata
listDatasets
List all datasets.
Inputs:
page,limit(pagination)
getDataset
Get a dataset by name.
Inputs:
datasetName(string, required): The dataset name
createDatasetItem
Create or update a dataset item.
Inputs:
datasetName(string, required): Target dataset nameinput(any, required): Item input dataexpectedOutput(any, optional): Expected outputmetadata(object, optional): Item metadatasourceTraceId(string, optional): Source trace IDsourceObservationId(string, optional): Source observation IDid(string, optional): Custom ID for upsert
listDatasetItems
List items in a dataset.
Inputs:
datasetName(string, required): Dataset namepage,limit(pagination)sourceTraceId(string, optional): Filter by source tracesourceObservationId(string, optional): Filter by source observation
getDatasetItem
Get a specific dataset item.
Inputs:
datasetItemId(string, required): The item ID
deleteDatasetItem
Delete a dataset item.
Inputs:
datasetItemId(string, required): The item ID to delete
createDatasetRunItem
Link a trace/observation to a dataset item for evaluation.
Inputs:
runName(string, required): Name of the dataset rundatasetItemId(string, required): Dataset item IDtraceId(string, required): Trace IDrunDescription(string, optional): Run descriptionobservationId(string, optional): Observation IDmetadata(object, optional): Run item metadata
listDatasetRuns
List runs for a dataset.
Inputs:
datasetName(string, required): Dataset namepage,limit(pagination)
getDatasetRun
Get a specific dataset run.
Inputs:
datasetName(string, required): Dataset namerunName(string, required): Run name
listSessions
List all sessions.
Inputs:
page,limit(pagination)fromTimestamp(string, optional): Start of time range (ISO 8601)toTimestamp(string, optional): End of time range (ISO 8601)
getSession
Get a specific session with its traces.
Inputs:
sessionId(string, required): The session IDincludeIO(boolean, optional): Include input/output in traces. Default:false
Returns: Session with associated traces.
Using with Official Langfuse MCP (Prompts)
This server provides observability tools (traces, scores, datasets). For prompt management, Langfuse provides a built-in MCP server that requires no installation.
Built-in Langfuse MCP (Recommended)
The Langfuse MCP server is built directly into Langfuse at /api/public/mcp. See the official documentation for setup instructions.
Using Both Servers Together
To use Langfuse observability (this server) alongside the official prompts MCP:
{
"mcpServers": {
"langfuse-observability": {
"command": "npx",
"args": ["-y", "langfuse-mcp-extended"],
"env": {
"LANGFUSE_PUBLIC_KEY": "pk-lf-...",
"LANGFUSE_SECRET_KEY": "sk-lf-..."
}
}
}
}Then configure the built-in Langfuse prompts MCP following the official guide.
Note: We're actively working with the Langfuse team to potentially integrate both servers. See Contributing for details.
Development
# Install dependencies
npm install
# Build
npm run build
# Run in development mode
npm run dev
# Run tests
npm test # Unit tests (59 tests)
npm run test:integration # Integration tests (18 tests)
npm run test:all # All tests
# Quality checks
npm run lint
npm run typecheckContributing
Contributions are welcome! This project aims to be integrated into the official Langfuse ecosystem.
Active discussions:
langfuse/langfuse#5646 - Integration discussion
langfuse/mcp-server-langfuse#14 - Feature request
How to contribute:
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
Author
Built by Javier Aguilar - AI Agent Architect specializing in multi-agent orchestration and MCP development.
License
MIT License - see LICENSE for details.
Related
Langfuse - Open source LLM observability
Langfuse MCP Server (Prompts) - Built-in prompt management MCP
Model Context Protocol - MCP specification
MCP Servers Registry - Official MCP servers
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/JaviMaligno/langfuse-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server