langfuse-mcp-extended
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level: debug, info, warn, error | info |
| LANGFUSE_BASE_URL | No | Langfuse instance URL (US Cloud, EU Cloud, or self-hosted) | https://cloud.langfuse.com |
| LANGFUSE_PUBLIC_KEY | Yes | Your Langfuse public key (pk-lf-...) | |
| LANGFUSE_SECRET_KEY | Yes | Your Langfuse secret key (sk-lf-...) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listTracesA | List traces with filtering and pagination. Returns trace metadata including latency, cost, and observation/score counts. |
| getTraceA | Get a specific trace with full details including all observations and scores. |
| deleteTraceA | Delete a specific trace. This action is irreversible. |
| listObservationsA | List observations (generations, spans, events) with cursor-based pagination. Includes usage metrics, costs, and latency. |
| getObservationA | Get a specific observation with all details including input/output, usage, costs, and timing. |
| createScoreA | Create a score for a trace or observation. Supports numeric, boolean, and categorical score types. |
| listScoresB | List scores with filtering. Supports both trace and observation scores. |
| getScoreB | Get a specific score by ID. |
| deleteScoreB | Delete a specific score. This action is irreversible. |
| createScoreConfigC | Create a score configuration that defines validation rules for scores. Supports numeric ranges, categorical values, and boolean types. |
| listScoreConfigsB | List all score configurations in the project. |
| getScoreConfigA | Get a specific score configuration by ID. |
| createDatasetB | Create a new dataset for evaluation. Datasets contain items with expected inputs/outputs for testing LLM applications. |
| listDatasetsC | List all datasets in the project. |
| getDatasetA | Get a dataset by name including its items and run names. |
| createDatasetItemB | Create or upsert a dataset item. Use id parameter for idempotent updates. |
| listDatasetItemsC | List items in a dataset with optional filtering. |
| getDatasetItemA | Get a specific dataset item by ID. |
| deleteDatasetItemA | Delete a specific dataset item. This action is irreversible. |
| createDatasetRunItemA | Create a dataset run item linking a trace/observation to a dataset item for evaluation. |
| listDatasetRunsB | List all runs for a specific dataset. |
| getDatasetRunA | Get a specific dataset run by name including its run items. |
| listSessionsC | List all sessions. Sessions group multiple traces from the same user interaction. |
| getSessionA | Get a specific session by ID including its traces. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Each tool targets a distinct resource-action pair (e.g., createDataset vs. createScore, listTraces vs. listScores). There is no ambiguity as resource types are clearly separated and operations are specific.
All tools follow a strict verb+noun pattern (e.g., createDataset, getDatasetItem, listObservations) using snake_case consistently. No mixing of styles or vague verbs.
24 tools cover the major resources (datasets, scores, traces, observations, sessions) with predictable CRUD operations. The count is well-scoped for a comprehensive observability server without being excessive.
The tool set lacks create endpoints for traces and observations, which are fundamental to the platform. While dataset items support upsert, the absence of trace and observation creation is a notable gap for a complete evaluation workflow.