Healthchecksio MCP vs Langfuse MCP
A side-by-side look at the Healthchecksio MCP and Langfuse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Healthchecksio MCP for monitoring work as a local process; choose Langfuse MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Healthchecksio MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HEALTHCHECKS_API_KEY, HEALTHCHECKS_API_URL, HEALTHCHECKS_PING_URL. - You want tools like
list_checks, get_check, create_check.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 52/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | HEALTHCHECKS_API_KEYHEALTHCHECKS_API_URLHEALTHCHECKS_PING_URL | LANGFUSE_PUBLIC_KEYLANGFUSE_SECRET_KEYLANGFUSE_HOSTLANGFUSE_MCP_READ_ONLY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 112 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 8 | 48 |
| Full listing | View Healthchecksio MCP | View Langfuse MCP |
Tools & capabilities
Healthchecksio MCP tools 8
list_checkslist checks, filter by tag/statusget_checkget a single check's detailscreate_checkcreate a new checkupdate_checkupdate a checklist_check_flipsup/down status historylist_channelsnotification channelslist_badgesbadge URLspingsend a heartbeat ping (success/fail/start/log)
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
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.
Healthchecksio MCP
{
"mcpServers": {
"healthchecksio-mcp": {
"command": "npx",
"args": [
"-y",
"github:nguyenhuy158/healthchecksio-mcp"
],
"env": {
"HEALTHCHECKS_API_KEY": "YOUR_HEALTHCHECKS_API_KEY_HERE",
"HEALTHCHECKS_API_URL": "YOUR_HEALTHCHECKS_API_URL_HERE",
"HEALTHCHECKS_PING_URL": "YOUR_HEALTHCHECKS_PING_URL_HERE"
}
}
}
}
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"
}
}
}
}
Frequently asked questions
Healthchecksio MCP is categorized under Monitoring and uses a local stdio subprocess. Langfuse MCP belongs to Monitoring and uses a local stdio subprocess. Pick Healthchecksio MCP for monitoring work and Langfuse MCP 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.
Healthchecksio MCP has no declared pricing — check the project's own site. Langfuse MCP is listed as free. Auth: api key required. 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 healthchecksio-mcp and avivsinai-langfuse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Healthchecksio MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Langfuse MCP has 65/100 (Great) with 6 views, 0 installs and 112 GitHub stars.