Langfuse MCP vs OneUptime
A side-by-side look at the Langfuse MCP and OneUptime MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Langfuse MCP for monitoring work as a local process; choose OneUptime for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Langfuse MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LANGFUSE_PUBLIC_KEY, LANGFUSE_SECRET_KEY, LANGFUSE_HOST, LANGFUSE_MCP_READ_ONLY. - You want tools like
list_annotation_queues, create_annotation_queue, get_annotation_queue.
Choose OneUptime when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
create_team, get_team, list_teams.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 65/100 · Great | 70/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | LANGFUSE_PUBLIC_KEYLANGFUSE_SECRET_KEYLANGFUSE_HOSTLANGFUSE_MCP_READ_ONLY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 112 | 7,757 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 48 | 199 |
| Full listing | View Langfuse MCP | View OneUptime |
Tools & capabilities
Langfuse MCP tools 48
list_annotation_queuesList annotation queues with pagination.create_annotation_queueCreate an annotation queue.get_annotation_queueGet a single annotation queue by ID.list_annotation_queue_itemsList items in an annotation queue.get_annotation_queue_itemGet a specific annotation queue item by queue and item ID.create_annotation_queue_itemCreate an annotation queue item.update_annotation_queue_itemUpdate the status of an annotation queue item.delete_annotation_queue_itemDelete an annotation queue item.create_annotation_queue_assignmentAssign a user to an annotation queue.delete_annotation_queue_assignmentUnassign a user from an annotation queue.list_datasetsList all datasets in the project with pagination. Returns metadata about datasets including name, description, item count, and timestamps. Args: ctx: Context object containing lifespan context with Langfuse client page: Page number for pagination (starts at 1) limit: Maximum items per page (max 100) Returns: A dictionary containing: - data: List of dataset metadata objects - metadata: Pagination info (page, limit, total)get_datasetGet a specific dataset by name. Retrieves dataset details including metadata and item count. Args: ctx: Context object containing lifespan context with Langfuse client name: The name of the dataset to fetch Returns: A dictionary containing dataset details: - id: Unique dataset identifier - name: Dataset name - description: Dataset description - metadata: Custom metadata - items: List of dataset items (if included by the API) - runs: List of dataset runs (if included by the API)- +36 more on the listing page
OneUptime tools 199
create_teamCreate a new Team in OneUptime. Returns the created Team object with its ID. Use this to add new Teams to your project. Note: projectId is inferred from your API key — you do not need to provide it.get_teamRetrieve a single Team by its unique ID from OneUptime. Use list_teams first if you need to find the ID.list_teamsList and search Teams from OneUptime with optional filtering, pagination, and sorting. Returns an array of Team objects plus the total matching count.update_teamUpdate an existing Team in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_team afterwards to see the updated record.delete_teamPermanently delete a Team from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.count_teamsCount the total number of Teams in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.create_labelCreate a new Label in OneUptime. Returns the created Label object with its ID. Use this to add new Labels to your project. Note: projectId is inferred from your API key — you do not need to provide it.get_labelRetrieve a single Label by its unique ID from OneUptime. Use list_labels first if you need to find the ID.list_labelsList and search Labels from OneUptime with optional filtering, pagination, and sorting. Returns an array of Label objects plus the total matching count.update_labelUpdate an existing Label in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_label afterwards to see the updated record.delete_labelPermanently delete a Label from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.count_labelsCount the total number of Labels in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.- +187 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Langfuse MCP
{
"mcpServers": {
"avivsinai-langfuse-mcp": {
"command": "uvx",
"args": [
"langfuse-mcp"
],
"env": {
"LANGFUSE_PUBLIC_KEY": "YOUR_LANGFUSE_PUBLIC_KEY_HERE",
"LANGFUSE_SECRET_KEY": "YOUR_LANGFUSE_SECRET_KEY_HERE",
"LANGFUSE_HOST": "YOUR_LANGFUSE_HOST_HERE",
"LANGFUSE_MCP_READ_ONLY": "YOUR_LANGFUSE_MCP_READ_ONLY_HERE"
}
}
}
}
OneUptime
{
"mcpServers": {
"oneuptime": {
"command": "npx",
"args": [
"-y",
"oneuptime"
]
}
}
}
Frequently asked questions
Langfuse MCP is categorized under Monitoring and uses a local stdio subprocess. OneUptime belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Langfuse MCP for monitoring work and OneUptime for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Langfuse MCP is listed as free. Auth: api key required. OneUptime has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add avivsinai-langfuse-mcp and oneuptime as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Langfuse MCP has a quality signal of 65/100 (Great) with 6 views, 0 installs and 112 GitHub stars. OneUptime has 70/100 (Great) with 2 views, 0 installs and 7,757 GitHub stars.