MCP Server vs Parseable MCP Server
A side-by-side look at the MCP Server and Parseable MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server for monitoring work as a local process; choose Parseable MCP Server 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 MCP Server 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:
MACKEREL_APIKEY. - You want tools like
list_alerts, get_alert, get_alert_logs.
Choose Parseable MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PARSEABLE_URL, PARSEABLE_API_KEY. - You want tools like
list_datasets, get_dataset_schema, get_dataset_info.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 65/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | MACKEREL_APIKEY | PARSEABLE_URLPARSEABLE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | 27 |
| Full listing | View MCP Server | View Parseable MCP Server |
Tools & capabilities
MCP Server tools 16
list_alertsRetrieve alerts from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Check currently active alerts - Get a list of alerts including closed alerts <examples> ### Get opening alerts ``` list_alerts() ``` ### Get all alerts ``` list_alerts(withClosed=true) ``` </examples>get_alertRetrieve a specific alert by ID from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Investigate a particular alert <examples> ### Get alert by ID ``` get_alert(alertId=3Yr) ``` </example>get_alert_logsRetrieve logs for a specific alert by ID from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - View status change history for a specific alert - Investigate alert transitions and their reasons <examples> ### Get alert logs for the alert ``` get_alert_logs(alertId=3Yr) ``` </example>list_dashboardsRetrieve all dashboards from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get a list of dashboards - Get ID and title of each dashboard <examples> ### Get all dashboards ``` list_dashboards() ``` </example>get_dashboardRetrieve a specific dashboard by ID from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get details of a specific dashboard - View dashboard configuration and widgets <examples> ### Get dashboard by ID ``` get_dashboard(dashboardId="3Yr") ``` </examples>update_dashboardUpdate a specific dashboard by ID in Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Modify dashboard title, memo, or URL path - Update dashboard widgets configuration <examples> ### Update dashboard ``` update_dashboard( dashboardId="3Yr", title="Updated Dashboard", memo="Updated memo", urlPath="updated path", widgets=[{ type="markdown", markdown="## Updated Markdown Widget", title="Updated Title", layout: { x: 0, y: 0, width: 6, height: 4 }, }] ) ``` </examples>list_hostsRetrieve hosts from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get a list of hosts - Filter hosts by various criteria (service, role, name, etc.) - Check host status and information <examples> ### Get all hosts (first 20) ``` list_hosts() ``` ### Get hosts for a specific role ``` list_hosts(service="web",role=["app"]) ``` ### Get hosts by status with pagination ``` list_hosts(status=["working","standby"], limit=10, offset=0) ``` ### Get hosts in summary format (reduced response size) ``` list_hosts(summary=true) ``` ### Get next page of hosts ``` list_hosts(limit=20, offset=20) ``` </examples>get_host_metricsRetrieve metrics data for a specific host from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get metrics data for a specific host - Analyze host performance over time 📊 AVAILABLE METRIC NAMES: - **Standard metrics (mackerel-agent)**: loadavg5, cpu.user, memory.used, disk.sda1.reads, network.eth0.rxBytes, etc. - **Custom metrics**: custom.myapp.* (user-defined metrics) - **AWS integration**: ec2.cpu.used, rds.database_connections.used, etc. - **Azure integration**: azure.virtual_machine.cpu.percent, azure.sql_database.cpu.percent, etc. - **GCP integration**: gce.instance.cpu.used, etc. <examples> ### Get CPU load average for a host ``` get_host_metrics(hostId="host123", name="loadavg5", from=1609459200, to=1609462800) ``` ### Get custom metric ``` get_host_metrics(hostId="host123", name="custom.myapp.response_time", from=1609459200, to=1609462800) ``` ### Get AWS EC2 CPU utilization ``` get_host_metrics(hostId="host123", name="ec2.cpu.used", from=1609459200, to=1609462800) ``` </examples>list_servicesRetrieve all services from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get a list of services - View service names, memos, and roles <examples> ### Get all services ``` list_services() ``` </examples>get_service_metricsRetrieve metrics data for a specific service from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - "Service metrics" are metrics that correspond to a service that consists of multiple hosts and their collective roles - The following can be visualized and monitored. - The total number of registered users in a service - The number of PVs for a website - Business related KPIs such as sales or the number of orders received from EC sites 📊 AVAILABLE METRIC NAMES: - **Custom metrics**: http.response_time, sales.count, analytics.page_view, etc. <examples> ### Get service response time ``` get_service_metrics(serviceName="web", name="__externalhttp.responsetime.<monitorId>", from=1609459200, to=1609462800) ``` ### Get service page views ``` get_service_metrics(serviceName="web", name="analytics.page_view", from=1609459200, to=1609462800) ``` </examples>list_monitorsRetrieve all monitor configurations from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get a list of all monitors - View monitor configurations <examples> ### Get all monitors ``` list_monitors() ``` </examples>get_monitorRetrieve a specific monitor configuration by ID from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get details of a specific monitor <examples> ### Get monitor by ID ``` get_monitor(monitorId="2cSZzK3XfmB") ``` </examples>- +4 more on the listing page
Parseable MCP Server tools 27
list_datasetsList all log datasetsget_dataset_schemaColumn names + typesget_dataset_infoMetadata (created_at, retention, time window)get_dataset_statsEvent count and storage bytessample_eventsMost recent N events (time-bounded, row-capped)query_sqlSQL `SELECT` over a time window. DDL/DML blocked. Auto-injects `LIMIT`.query_promqlPromQL instant or range query against a metrics datasetlist_alertsList all alerts with state, severity, tagsget_alertFull config for one alertlist_alert_tagsAll alert tags in useenable_alertEnable an alertdisable_alertDisable an alert- +15 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.
MCP Server
{
"mcpServers": {
"mcp-server-180": {
"command": "npx",
"args": [
"-y",
"@mackerel/mcp-server"
],
"env": {
"MACKEREL_APIKEY": "YOUR_MACKEREL_APIKEY_HERE"
}
}
}
}
Parseable MCP Server
{
"mcpServers": {
"parseable-mcp-server": {
"command": "npx",
"args": [
"-y",
"@parseable/parseable-mcp-server"
],
"env": {
"PARSEABLE_URL": "YOUR_PARSEABLE_URL_HERE",
"PARSEABLE_API_KEY": "YOUR_PARSEABLE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
MCP Server is categorized under Monitoring and uses a local stdio subprocess. Parseable MCP Server belongs to Monitoring and uses a local stdio subprocess. Pick MCP Server for monitoring work and Parseable MCP Server 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.
MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Parseable MCP Server 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 mcp-server-180 and parseable-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server has a quality signal of 65/100 (Great) with 1 views, 0 installs and 7 GitHub stars. Parseable MCP Server has 57/100 (Good) with 1 views, 0 installs and 4 GitHub stars.