Parseable MCP Server logo

Parseable MCP Server

Query Parseable logs and metrics, inspect alerting and RBAC, and manage alerts through MCP tools.

Install Parseable MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "parseable-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@parseable/parseable-mcp-server"
      ],
      "env": {
        "PARSEABLE_URL": "YOUR_VALUE_HERE",
        "PARSEABLE_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @parseable/parseable-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 6d ago.

Overview

The parseable-mcp-server MCP server connects MCP clients to Parseable for dataset discovery, SQL and PromQL queries, alert inspection, and alert management. It supports local stdio connections with environment-based credentials and Streamable HTTP for hosted or remote deployments. Use it when an agent needs bounded access to Parseable logs, metrics, alert targets, health data, or read-only administration details. SQL mutations and DDL are blocked, and query results receive row limits.

Use cases

  • Query log datasets with bounded SQL
  • Inspect schemas, retention, and storage statistics
  • Create and manage Parseable alerts
  • Check cluster health and query performance
  • Review users, roles, and alert targets

Key features

  • Dataset discovery and metadata inspection
  • Bounded SQL SELECT and PromQL queries
  • Alert and notification-target management
  • Connectivity and SQL explanation diagnostics
  • Read-only RBAC and cluster administration tools
  • Stdio and Streamable HTTP transports

Tools27

What Parseable MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~327 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14h ago via OSV.dev · @parseable/parseable-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads703Package downloads in the last 30 days.
Last commit19d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed27Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Parseable MCP Server works

What parseable-mcp-server MCP server does

The parseable-mcp-server MCP server exposes Parseable operations as tools that an MCP-capable client can call. It can enumerate log datasets, inspect schemas and metadata, report event counts and storage usage, and return recent sample events. Dataset queries support SQL SELECT statements over a time window and PromQL instant or range queries for metrics datasets.

Alert workflows cover listing alerts and tags, retrieving an alert configuration, enabling or disabling alerts, and creating alerts through a guided eight-question flow with confirmation before submission. The server can also list and inspect Slack, webhook, and Alertmanager targets, or create a new target. The evaluate_alert operation forces an evaluation and may send real notifications, so it should be used with care.

Additional tools provide connectivity and query diagnostics, including ping and SQL EXPLAIN. Read-only RBAC tools expose users, user roles, role names, privileges, and the default role. In distributed Parseable deployments, administrative tools report cluster status and aggregate ingest, query, and storage metrics; another tool returns a dataset's retention policy.

How it works

The parseable-mcp-server MCP server supports two transports. In stdio mode, the MCP client starts the process and the server reads Parseable connection settings from environment variables. In HTTP mode, one process serves a setup page and the Streamable HTTP MCP endpoint. Requests authenticate with X-API-Key. Cloud requests identify cloud mode, while self-hosted requests provide the Parseable URL; self-hosted is the default when a mode header is omitted.

For cloud authentication, the HTTP server validates API keys through Parseable Cloud and keeps resolved routing information in a bounded in-memory cache for up to the configured TTL. Self-hosted HTTP requests forward the supplied API key to the selected Parseable instance. Private and loopback target URLs are rejected by default in HTTP mode.

SQL execution is restricted to SELECT queries. DDL and DML are blocked, an automatic LIMIT is applied, and a configurable maximum row count is enforced. Query requests also use a configurable HTTP timeout.

Setup and configuration

Run npx -y @parseable/parseable-mcp-server init for interactive local setup. The command can detect Claude Desktop or Cursor and write client configuration. For scripted stdio setup, provide the client, Parseable URL, and API key explicitly.

Set PARSEABLE_URL and PARSEABLE_API_KEY for a self-hosted stdio connection. PARSEABLE_DEFAULT_DATASET supplies an advisory dataset name, while PARSEABLE_MAX_ROWS and PARSEABLE_QUERY_TIMEOUT_MS control query bounds and timeout behavior. HTTP mode listens on port 8787 by default and can run from the built Node output or the supplied Docker image.

Cursor's Marketplace plugin uses PARSEABLE_MODE and PARSEABLE_API_KEY; self-hosted mode also requires PARSEABLE_URL. Cloud mode omits the URL. HTTP clients can connect using the /mcp endpoint and the documented request headers. Set PARSEABLE_MCP_ALLOW_PRIVATE=true only when a trusted deployment must reach private Parseable addresses.

Limitations and notes

The server does not provide unrestricted SQL execution: write statements and schema-changing statements are rejected. Sampling and query results are bounded by time and row limits. The alert evaluation tool can trigger external notifications. RBAC and cluster tools are read-only, while alert and alert-target tools include configuration changes.

OpenTelemetry export is optional and can send traces to a Parseable OTLP endpoint when enabled. Cloud routing cache entries are disposable, so process restarts or cache misses cause cloud resolution to run again.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Parseable MCP Server

parseable-mcp-server is an MCP server that connects MCP-capable clients to Parseable. Its main tools discover datasets, inspect schemas and metadata, run bounded SQL SELECT or PromQL queries, manage alerts and alert targets, check health, and read RBAC or cluster information. It supports stdio and Streamable HTTP transports.

Run `npx -y @parseable/parseable-mcp-server init` for interactive stdio setup. It can detect Claude Desktop or Cursor and write configuration files. For HTTP deployments, build the project and run `node dist/server.js http`, or build and run the provided Docker image.

Yes, parseable-mcp-server supports Cursor through stdio configuration or its Marketplace plugin. The plugin uses `PARSEABLE_MODE` and `PARSEABLE_API_KEY`; self-hosted connections also use `PARSEABLE_URL`. Cursor can also connect to a remote Streamable HTTP endpoint.

No, SQL writes and DDL are blocked. The `query_sql` tool accepts SELECT queries over a time window, automatically adds a LIMIT, and applies the configured maximum row count. Use the separate alert tools for supported alert configuration changes.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewParseable MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/parseable-mcp-server?style=directory)](https://allmcps.com/mcp/parseable-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/parseable-mcp-server"><img src="https://allmcps.com/api/badge/parseable-mcp-server?style=directory" alt="Parseable MCP Server on AllMCPs" /></a>