Skip to main content
Glama
mgcrea

mcp-langfuse

by mgcrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LANGFUSE_HOSTNoInstance URL, e.g. https://langfuse.example.com. Else the keys file's host, else Langfuse Cloud.
LANGFUSE_DEBUGNoSet to 1 to log each request to stderr.
LANGFUSE_PROJECTNoThe name (or id) that the single LANGFUSE_PUBLIC_KEY/LANGFUSE_SECRET_KEY pair is filed under, and checked against.
LANGFUSE_BASE_URLNoAccepted as an alias of LANGFUSE_HOST.
LANGFUSE_PROJECTSNoJSON map of project name → key pair, e.g. {"sales": {"publicKey": "pk-lf-…", "secretKey": "sk-lf-…", "id": "…"}}.
LANGFUSE_KEYS_FILENoKeys file path. Defaults to $XDG_CONFIG_HOME/langfuse-mcp/keys.json.
LANGFUSE_PUBLIC_KEYNoA single project's public key (pk-lf-…), from Project Settings → API Keys.
LANGFUSE_SECRET_KEYNoThe secret key (sk-lf-…) matching LANGFUSE_PUBLIC_KEY.
LANGFUSE_MAX_RETRIESNoRetry budget for 429/5xx. Defaults to 3.3
LANGFUSE_ALLOW_WRITESNoSet to 1 to let langfuse_request send POST/PUT/PATCH/DELETE.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
langfuse_auth_statusA

List the Langfuse projects this server can read — the names the other tools' project argument takes — and check each key against the project it is filed under. Keys are project-scoped, so this is the first thing to check when data looks wrong or missing. Also reports the Langfuse version, whether it runs in v4 events-only mode (no /traces or /sessions), whether writes are enabled, and, when something is not configured, exactly what to set. Makes one small API call per project, plus two.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation4/5

With only one tool exposed there is no possible confusion between tools, so selection is unambiguous. However, the description repeatedly refers to "the other tools' `project` argument," which do not exist in this set, so an agent may waste effort looking for tools that aren't there.

Naming Consistency4/5

The single name `langfuse_auth_status` is clear, prefixed, and uses consistent snake_case. There is no multi-tool set to verify a pattern against, so consistency can only be judged on readability.

Tool Count2/5

A Langfuse observability server exposing exactly one diagnostic/status tool is far too thin for the apparent scope (projects, traces, sessions, scores). The description itself implies a larger intended surface, making this a notable under-scoping rather than a deliberately minimal server.

Completeness1/5

There are no tools to actually read Langfuse data — no trace, session, observation, score, or project listing operations — despite the tool describing itself as the entry point to a broader set. An agent can check auth status and then hit a dead end for every real workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources