# Langfuse v4.68.0 adds MCP connection tool and gateway key controls

published: 2026-10-22T15:05:58.880Z
topic: infrastructure
source: https://github.com/langfuse/langfuse/releases/tag/v4.68.0
url: https://aiagentnews.io/stories/langfuse-v4-68-0-adds-mcp-connection-tool-and-gateway-key-controls

Langfuse released v4.68.0 with a new listLlmConnections tool for its MCP server and several changes to AI gateway keys. The release also adds managed skills loading, new Topics views, and a set of security and dependency fixes.

Langfuse's v4.68.0 release adds a listLlmConnections tool to its MCP server. The AI gateway also gets several changes: members can create their own gateway API keys, owners and admins can issue keys as a service account, and a global enable flag plus a derived JWT public key and key ID support self-hosting. Gateway keys are now revoked when their user leaves the organization.

The agent side gains managed skills loaded from Langfuse, and skills setup and usage filtering were streamlined. Topics results get Treemap and Grid views, and the cluster map returns as a third view. Blob export can now include opt-in score metadata and provenance field groups.

Fixes cover escaping LIKE wildcards in evaluation, dataset and Postgres table filters, and version bumps for follow-redirects, vite and other dependencies. Legacy ingestion is now limited to scores for new organizations, and audit logs are restricted to enterprise plans.

## Why it matters if you build agents

Agents that connect to Langfuse over MCP can now list LLM connections with the listLlmConnections tool. Teams running self-hosted AI gateways get an enable flag and JWT key details, but keys tied to users who leave an organization are now revoked. Code that depends on LIKE-style filters or legacy ingestion for existing organizations should be checked against these changes.