Developer · Local MCP server
Langfuse API
Langfuse public API (Cloud and self-hosted): traces, prompts, datasets and gated writes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.rodrigorjsf/langfuse-api-mcp- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm, OCI image (Docker), MCP Bundle (.mcpb)
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- rodrigorjsf (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/rodrigorjsf) · how
- Website
- github.com/rodrigorjsf/langfuse-api-mcp
- Repository
- github.com/rodrigorjsf/langfuse-api-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | langfuse-api-mcp | 0.1.0 | stdio |
| OCI image (Docker)runtime: docker | ghcr.io/rodrigorjsf/langfuse-api-mcp:0.1.0 | - | stdio |
| MCP Bundle (.mcpb) | https://github.com/rodrigorjsf/langfuse-api-mcp/releases/download/v0.1.0/langfuse-mcp_0.1.0.mcpbSHA-256 checksum stated | - | stdio |
How to connect Langfuse API
Langfuse API runs locally from a Node.js package published to the npm registry: langfuse-api-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y langfuse-api-mcp@0.1.0. It reads these environment variables: LANGFUSE_PUBLIC_KEY (required, secret), LANGFUSE_SECRET_KEY (required, secret), LANGFUSE_BASE_URL (required) and LANGFUSE_CA_CERT; set them in the client's configuration for this server.
Langfuse API runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/rodrigorjsf/langfuse-api-mcp:0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e LANGFUSE_PUBLIC_KEY -e LANGFUSE_SECRET_KEY -e LANGFUSE_BASE_URL ghcr.io/rodrigorjsf/langfuse-api-mcp:0.1.0. It reads these environment variables: LANGFUSE_PUBLIC_KEY (required, secret), LANGFUSE_SECRET_KEY (required, secret) and LANGFUSE_BASE_URL (required); set them in the client's configuration for this server.
Langfuse API runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/rodrigorjsf/langfuse-api-mcp/releases/download/v0.1.0/langfuse-mcp_0.1.0.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"langfuse-api-mcp": {
"command": "npx",
"args": [
"-y",
"langfuse-api-mcp@0.1.0"
],
"env": {
"LANGFUSE_PUBLIC_KEY": "<secret>",
"LANGFUSE_SECRET_KEY": "<secret>",
"LANGFUSE_BASE_URL": "<value>",
"LANGFUSE_CA_CERT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Lan DirectBrowser MCP: the app under test egresses via the real ISP while the agent stays on the VPN. | Local · stdio |
| LanceRoylo MCPAEO scoring, llms.txt audit, and agent-readiness checks for AI agents. | Local · stdio |
| LandLens rental recordsOwner of record, code violations, evictions and tenant reviews for US college-town rentals. | Remote · HTTPLive check: ✓ handshake |
| Langchain MCPLangChain/LangGraph/DeepAgents knowledge + LangGraph agent debugging (Polly-like) | Local · stdio |
| LastestRun visual regression tests, review diffs, and manage baselines on a Lastest instance. | Local · stdio |
| LastPingMonitoring that agents set up for themselves: cron jobs, CI/CD pipelines and AI agent runs. | Remote · HTTPLive check: sign-in required |
| lastseen mortalityCheck whether an npm package, GitHub Action, MCP server or Docker image is dead or abandoned. | Local · stdio |
| LatchkeyTriage failing GitHub Actions jobs and see what self-heal repaired, in natural language. | Remote · HTTPLive check: sign-in required |