@last9/mcp-server 0.5.1 → 0.7.0

package/README.md

@@ -1,504 +1,132 @@
 # Last9 MCP Server
 
 ![last9 mcp demo](mcp-demo.gif)
-A [Model Context Protocol](https://modelcontextprotocol.io/) server
-implementation for [Last9](https://last9.io/mcp/) that enables AI agents to
-seamlessly bring real-time production context — logs, metrics, and traces — into
-your local environment to auto-fix code faster.
 
-- [View demo](https://www.youtube.com/watch?v=AQH5xq6qzjI)
-- Read our
-  [announcement blog post](https://last9.io/blog/launching-last9-mcp-server/)
+Your AI agent doesn't know what's broken in production. This fixes that.
 
-## Quick Links
+[Last9 MCP Server](https://last9.io/mcp/) connects Claude, Cursor, Windsurf, and any other MCP-capable AI assistant directly to your production observability data — logs, metrics, traces, exceptions, database queries, alerts, and deployments. The agent stops guessing and starts reading the actual signal.
 
-- [Status](#status)
-- [Installation](#installation)
-- [Configuration](#configuration)
-- [Usage](#usage)
-- [Tools Documentation](#tools-documentation)
-- [Development](#development)
-- [Testing](#testing)
-- [Badges](#badges)
+- [Watch the demo](https://www.youtube.com/watch?v=AQH5xq6qzjI)
+- [Announcement post](https://last9.io/blog/launching-last9-mcp-server/)
 
-## Installation
+---
 
-You can connect to Last9 MCP in two ways:
+## Start in 30 seconds (Hosted)
 
-### Recommended: Managed MCP over HTTP
+No binary to install. No tokens to manage. One URL, OAuth in your browser, done.
 
-This is the easiest and cleanest setup. You do not need to run a local binary.
-You'll need a **Client Token** (MCP type) — see [Getting your credentials](#getting-your-credentials) below. Your org slug is in your Last9 URL: `app.last9.io/<org_slug>/...`
+Find your org slug in your Last9 URL: `app.last9.io/<org_slug>/...`
+
+### Claude Code
 
 ```bash
-claude mcp add --transport http last9 https://app.last9.io/api/v4/organizations/<organization_slug>/mcp \
-  --header "X-LAST9-API-TOKEN: Bearer <last9_api_token>"
+claude mcp add --transport http last9 https://app.last9.io/api/v4/organizations/<org_slug>/mcp
 ```
 
-Or add it directly to your MCP client config:
+Type `/mcp`, select last9, authenticate. That's it.
+
+### Cursor
+
+**Settings > MCP > Add New MCP Server:**
 
 ```json
 {
   "mcpServers": {
     "last9": {
       "type": "http",
-      "url": "https://app.last9.io/api/v4/organizations/<organization_slug>/mcp",
-      "headers": {
-        "X-LAST9-API-TOKEN": "Bearer <last9_api_token>"
-      }
+      "url": "https://app.last9.io/api/v4/organizations/<org_slug>/mcp"
     }
   }
 }
 ```
 
-### Local Installation (STDIO fallback)
+Click **Connect**, complete OAuth.
 
-Use this only if your client needs a local STDIO server process.
+### VS Code
 
-#### Homebrew
+Requires v1.99+. Open Command Palette → **MCP: Add Server**, paste the URL, authenticate.
 
-```bash
-brew update
-brew install last9/tap/last9-mcp
-brew upgrade last9/tap/last9-mcp
-last9-mcp --version
-```
-
-#### NPM
+Or directly in `settings.json`:
 
-```bash
-# Install globally
-npm install -g @last9/mcp-server@latest
-# Or run directly with npx
-npx -y @last9/mcp-server@latest
+```json
+{
+  "mcp": {
+    "servers": {
+      "last9": {
+        "type": "http",
+        "url": "https://app.last9.io/api/v4/organizations/<org_slug>/mcp"
+      }
+    }
+  }
+}
 ```
 
-#### GitHub Releases (Windows / manual install)
-
-Download the binary for your platform from [GitHub Releases](https://github.com/last9/last9-mcp-server/releases/latest):
-
-| Platform | Archive |
-|----------|---------|
-| Windows (x64) | `last9-mcp-server_Windows_x86_64.zip` |
-| Windows (ARM64) | `last9-mcp-server_Windows_arm64.zip` |
-| Linux (x64) | `last9-mcp-server_Linux_x86_64.tar.gz` |
-| Linux (ARM64) | `last9-mcp-server_Linux_arm64.tar.gz` |
-| macOS (x64) | `last9-mcp-server_Darwin_x86_64.tar.gz` |
-| macOS (ARM64) | `last9-mcp-server_Darwin_arm64.tar.gz` |
-
-Extract the archive. On Windows the binary is `last9-mcp-server.exe`. Use the full path to the binary in your MCP client config (see [Windows example](#windows-example-claude-desktop) below).
-
-> On Windows, [NPM](#npm) is easier to set up (no path management needed), or use the [hosted HTTP transport](#recommended-managed-mcp-over-http) to skip local installation entirely.
-
-## Getting Your Credentials
-
-### For hosted MCP (recommended)
-
-You need a **Client Token** with MCP type. Only **admins** can create tokens. If you're not an admin, ask your admin to create one or grant you admin access via [User Access settings](https://app.last9.io/settings/user-access).
-
-1. Go to [Ingestion Tokens](https://app.last9.io/control-plane/ingestion-tokens)
-2. Click **New Ingestion Token**
-3. Set **Token Type** to **Client**
-4. Set **Client Type** to **MCP**
-5. Enter a name (e.g., `claude-desktop`, `cursor`)
-6. Click **Create** — copy the token immediately (shown only once)
-
-Your **organization slug** is in your Last9 URL: `https://app.last9.io/<org_slug>/...`
-
-### For local binary (STDIO mode)
-
-You need a **Refresh Token** with Write permissions. Only **admins** can create them.
-
-1. Go to [API Access](https://app.last9.io/settings/api-access)
-2. Click **Generate Token** with Write permissions
-3. Copy the token
-
-## Status
-
-Works with Claude desktop app, or Cursor, Windsurf, and VSCode (Github Copilot)
-IDEs. Implements the following MCP
-[tools](https://modelcontextprotocol.io/docs/concepts/tools):
-**Observability & APM Tools:**
-
-- `get_exceptions`: Get the list of exceptions.
-- `get_service_summary`: Get service summary with throughput, error rate, and response time.
-- `get_service_environments`: Get available environments for services.
-- `get_service_performance_details`: Get detailed performance metrics for a service.
-- `get_service_operations_summary`: Get operations summary for a service.
-- `get_service_dependency_graph`: Get service dependency graph showing incoming/outgoing dependencies.
-  **Prometheus/PromQL Tools:**
-- `prometheus_range_query`: Execute PromQL range queries for metrics data.
-- `prometheus_instant_query`: Execute PromQL instant queries for metrics data.
-- `prometheus_label_values`: Get label values for PromQL queries.
-- `prometheus_labels`: Get available labels for PromQL queries.
-  **Logs Management:**
-- `get_logs`: Get logs filtered by service name and/or severity level.
-- `get_drop_rules`: Get drop rules for logs that determine what logs get
-  filtered out at [Last9 Control Plane](https://last9.io/control-plane)
-- `add_drop_rule`: Create a drop rule for logs at
-  [Last9 Control Plane](https://last9.io/control-plane)
-- `get_service_logs`: Get raw log entries for a specific service over a time range. Can apply filters on severity and body.
-- `get_log_attributes`: Get available log attributes (labels) for a specified time window.
-  **Traces Management:**
-- `get_traces`: Retrieve traces using JSON pipeline queries for advanced filtering.
-- `get_service_traces`: Retrieve traces by trace ID or service name with time range filtering.
-- `get_trace_attributes`: Get available trace attributes (series) for a specified time window.
-  **Change Events:**
-- `get_change_events`: Get change events from the last9_change_events prometheus metric over a given time range.
-  **Alert Management:**
-- `get_alert_config`: Get alert configurations (alert rules) from Last9.
-- `get_alerts`: Get currently active alerts from Last9 monitoring system.
-
-## Tools Documentation
-
-### Time Input Standard
-
-- For relative windows, prefer `lookback_minutes` (up to 20160 minutes = 14 days).
-- For absolute windows, use `start_time_iso`, `end_time_iso`, or `time_iso` in RFC3339/ISO8601 (for example, `2026-02-09T15:04:05Z`).
-- If both relative and absolute inputs are provided, absolute time inputs take precedence.
-- Legacy `YYYY-MM-DD HH:MM:SS` is accepted only for compatibility.
-- If a lookback limit error occurs, retry using explicit `start_time_iso`/`end_time_iso` timestamps.
-
-### Deep Links
-
-Most tools return a `deep_link` field in the response metadata. This is a direct URL to the relevant Last9 dashboard view for the queried data — click it to open the corresponding alerts, logs, traces, or APM dashboard page.
-
-### Attribute Caching
-
-The server automatically fetches and caches available log and trace attribute names at startup (with a 10-second timeout) and refreshes the cache every 2 hours in the background. These dynamic attributes are embedded into the `get_logs`, `get_traces`, and `prometheus_range_query` tool descriptions, so AI assistants always see up-to-date field names when constructing queries.
-
-### get_exceptions
-
-Retrieves server-side exceptions over a specified time range.
-Parameters:
-
-- `limit` (integer, optional): Maximum number of exceptions to return.
-  Default: 20.
-- `lookback_minutes` (integer, recommended): Number of minutes to look back from
-  now. Default: 60. Range: 1–20160 (14 days). Examples: 60, 30, 15.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to use lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `service_name` (string, optional): Filter exceptions by service name (e.g., api-service).
-- `span_name` (string, optional): Name of the span to filter by.
-- `deployment_environment` (string, optional): Filter exceptions by deployment environment from resource attributes (e.g., production, staging).
-
-### get_service_summary
-
-Get service summary over a given time range. Includes service name, environment, throughput, error rate, and response time. All values are p95 quantiles over the time range.
-Parameters:
-
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to default to end_time_iso - 1 hour.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `env` (string, optional): Environment to filter by. Defaults to 'prod'.
-
-### get_service_environments
-
-Get available environments for services. Returns an array of environments that can be used with other APM tools.
-Parameters:
-
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to default to end_time_iso - 1 hour.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-  Note: All other APM tools that retrieve service information (like `get_service_performance_details`, `get_service_dependency_graph`, `get_service_operations_summary`, `get_service_summary`) require an `env` parameter. This parameter must be one of the environments returned by this tool. If this tool returns an empty array, use an empty string `""` for the env parameter.
-
-### get_service_performance_details
-
-Get detailed performance metrics for a specific service over a given time range.
-Parameters:
-
-- `service_name` (string, required): Name of the service to get performance details for.
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now. Default: 60. Range: 1–20160 (14 days).
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to use lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `env` (string, optional): Environment to filter by. Defaults to 'prod'.
-  Returns: throughput, error rate, p50/p90/p95/avg/max response times, apdex score, availability, top operations, and top errors.
-
-### get_service_operations_summary
-
-Get a summary of operations inside a service over a given time range. Returns operations like HTTP endpoints, database queries, messaging producer and HTTP client calls.
-Parameters:
-
-- `service_name` (string, required): Name of the service to get operations summary for.
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now. Default: 60. Range: 1–20160 (14 days).
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to use lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `env` (string, optional): Environment to filter by. Defaults to 'prod'.
-  Each operation includes: throughput (rpm), error rate (rpm), error percentage, and p50/p90/p95/avg/max response times (ms).
-
-### get_service_dependency_graph
-
-Get details of the throughput, response times and error rates of incoming, outgoing and infrastructure components of a service. Useful for analyzing cascading effects of errors and performance issues.
-Parameters:
-
-- `service_name` (string, optional): Name of the service to get the dependency graph for.
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now. Default: 60. Range: 1–20160 (14 days).
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to use lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `env` (string, optional): Environment to filter by. Defaults to 'prod'.
-  Each node includes: throughput (rpm), error rate (rpm), error percentage, and p50/p90/p95/avg/max response times (ms).
-
-### prometheus_range_query
-
-Perform a Prometheus range query to get metrics data over a specified time range. Recommended to check available labels first using `prometheus_labels` tool.
-Parameters:
-
-- `query` (string, required): The range query to execute.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to default to now - 60 minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-
-### prometheus_instant_query
-
-Perform a Prometheus instant query to get metrics data at a specific time. Typically should use rollup functions like sum_over_time, avg_over_time, quantile_over_time over a time window.
-Parameters:
-
-- `query` (string, required): The instant query to execute.
-- `time_iso` (string, optional): Time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to default to current time.
-
-### prometheus_label_values
-
-Return the label values for a particular label and PromQL filter query. Similar to Prometheus /label_values call.
-Parameters:
-
-- `match_query` (string, required): A valid PromQL filter query.
-- `label` (string, required): The label to get values for.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to default to now - 60 minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-
-### prometheus_labels
-
-Return the labels for a given PromQL match query. Similar to Prometheus /labels call.
-Parameters:
-
-- `match_query` (string, required): A valid PromQL filter query.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to default to now - 60 minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-
-### get_logs
-
-Gets logs filtered by service name and/or severity level within a specified time range. This tool now uses the advanced v2 logs API with physical index optimization for better performance.
-**Note**: This tool now requires a `service_name` parameter and internally uses the same advanced infrastructure as `get_service_logs`.
-Parameters:
-
-- `service_name` (string, required): Name of the service to get logs for.
-- `severity` (string, optional): Severity of the logs to get (automatically converted to severity_filters format).
-- `lookback_minutes` (integer, recommended): Number of minutes to look back from now. Default: 60. Range: 1–20160 (14 days). Examples: 60, 30, 15.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to use lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `limit` (integer, optional): Maximum number of logs to return. Default: 20.
-- `env` (string, optional): Environment to filter by. Use "get_service_environments" tool to get available environments.
-
-### get_drop_rules
-
-Gets drop rules for logs, which determine what logs get filtered out from
-reaching Last9.
-
-### add_drop_rule
-
-Adds a new drop rule to filter out specific logs at
-[Last9 Control Plane](https://last9.io/control-plane)
-Parameters:
-
-- `name` (string, required): Name of the drop rule.
-- `filters` (array, required): List of filter conditions to apply. Each filter
-  has:
-  - `key` (string, required): The key to filter on. Only attributes and
-    resource.attributes keys are supported. For resource attributes, use format:
-    resource.attributes[key_name] and for log attributes, use format:
-    attributes[key_name] Double quotes in key names must be escaped.
-  - `value` (string, required): The value to filter against.
-  - `operator` (string, required): The operator used for filtering. Valid
-    values:
-    - "equals"
-    - "not_equals"
-  - `conjunction` (string, required): The logical conjunction between filters.
-    Valid values:
-    - "and"
-
-### get_alert_config
-
-Get alert configurations (alert rules) from Last9. Returns all configured alert rules including their conditions, labels, and annotations.
-Parameters:
-None - This tool retrieves all available alert configurations.
-Returns information about:
-
-- Alert rule ID and name
-- Primary indicator being monitored
-- Current state and severity
-- Algorithm used for alerting
-- Entity ID and organization details
-- Properties and configuration
-- Creation and update timestamps
-- Group timeseries notification settings
-
-### get_alerts
-
-Get currently active alerts from Last9 monitoring system. Returns all alerts that are currently firing or have fired recently within the specified time window.
-Parameters:
-
-- `time_iso` (string, optional): Evaluation time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Preferred.
-- `timestamp` (integer, optional): Unix timestamp for the query time. Deprecated alias.
-- `window` (integer, optional): Time window in seconds to look back for alerts. Defaults to 900 seconds (15 minutes). Range: 60-86400 seconds.
-- `lookback_minutes` (integer, optional): Relative time window in minutes. Used only when `window` is not provided. Range: 1-1440.
-  Returns information about:
-- Alert rule details (ID, name, group, type)
-- Current state and severity
-- Last fired timestamp and duration
-- Rule properties and configuration
-- Alert instances with current values
-- Metric degradation information
-- Group labels and annotations for each instance
-
-### get_service_logs
-
-Get raw log entries for a specific service over a time range. This tool retrieves actual log entries including log messages, timestamps, severity levels, and other metadata. Useful for debugging issues, monitoring service behavior, and analyzing specific log patterns.
-Parameters:
-
-- `service_name` (string, required): Name of the service to get logs for.
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now. Default: 60. Range: 1–20160 (14 days). Examples: 60, 30, 15.
-- `limit` (integer, optional): Maximum number of log entries to return. Default: 20.
-- `env` (string, optional): Environment to filter by. Use "get_service_environments" tool to get available environments.
-- `severity_filters` (array, optional): Array of severity patterns to filter logs (e.g., ["error", "warn"]). Uses OR logic.
-- `body_filters` (array, optional): Array of message content patterns to filter logs (e.g., ["timeout", "failed"]). Uses OR logic.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to default to now - lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-  Filtering behavior:
-- Multiple filter types are combined with AND logic (service AND severity AND body)
-- Each filter array uses OR logic (matches any pattern in the array)
-  Examples:
-- service_name="api" + severity_filters=["error"] + body_filters=["timeout"] → finds error logs containing "timeout"
-- service_name="web" + body_filters=["timeout", "failed", "error 500"] → finds logs containing any of these patterns
-
-### get_log_attributes
-
-Get available log attributes (labels) for a specified time window. This tool retrieves all attribute names that exist in logs during the specified time range, which can be used for filtering and querying logs.
-Parameters:
-
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now for the time window. Default: 15. Examples: 15, 30, 60.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to use lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `region` (string, optional): AWS region to query. Leave empty to use default from configuration. Examples: ap-south-1, us-east-1, eu-west-1.
-  Returns:
-- List of log attributes grouped into two categories:
-  - Log Attributes: Standard log fields like service, severity, body, level, etc.
-  - Resource Attributes: Resource-related fields prefixed with "resource\_" like resource_k8s.pod.name, resource_service.name, etc.
-
-### get_traces
-
-Execute advanced trace queries using JSON pipeline syntax for complex filtering and aggregation. This tool provides powerful querying capabilities for traces using a pipeline-based approach with filters, aggregations, and transformations.
-Parameters:
-
-- `tracejson_query` (array, required): JSON pipeline query for traces. Use the tracejson_query_builder prompt to generate JSON pipeline queries from natural language.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z).
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z).
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now. Default: 60. Range: 1–20160 (14 days).
-- `limit` (integer, optional): Maximum number of traces to return. Default: 20. Range: 1-100.
-  This tool supports complex queries with multiple filter conditions, aggregations, and custom processing pipelines for advanced trace analysis.
-
-### get_service_traces
-
-Retrieve traces from Last9 by trace ID or service name. This tool allows you to get specific traces either by providing a trace ID for a single trace, or by providing a service name to get all traces for that service within a time range.
-Parameters:
-
-- `trace_id` (string, optional): Specific trace ID to retrieve. Cannot be used with service_name.
-- `service_name` (string, optional): Name of service to get traces for. Cannot be used with trace_id.
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now. Default: 60. Range: 1–20160 (14 days). Examples: 60, 30, 15.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to use lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `limit` (integer, optional): Maximum number of traces to return. Default: 10. Range: 1-100.
-- `env` (string, optional): Environment to filter by. Use "get_service_environments" tool to get available environments.
-  Usage rules:
-- Exactly one of `trace_id` or `service_name` must be provided (not both, not neither)
-- Time range filtering only applies when using `service_name`
-  Examples:
-- trace_id="abc123def456" - retrieves the specific trace
-- service_name="payment-service" + lookback_minutes=30 - gets all payment service traces from last 30 minutes
-  Returns trace data including trace IDs, spans, duration, timestamps, and status information.
-
-### get_trace_attributes
-
-Get available trace attributes (series) for a specified time window. This tool retrieves all attribute names that exist in traces during the specified time range, which can be used for filtering and querying traces.
-Parameters:
+### Windsurf
 
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now for the time window. Default: 15. Examples: 15, 30, 60.
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to use lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `region` (string, optional): AWS region to query. Leave empty to use default from configuration. Examples: ap-south-1, us-east-1, eu-west-1.
-  Returns:
-- An alphabetically sorted list of all available trace attributes (e.g., http.method, http.status_code, db.name, resource_service.name, duration, etc.)
+**Settings > Cascade > Open MCP Marketplace > gear icon (`mcp_config.json`):**
 
-### get_change_events
-
-Get change events from the last9_change_events prometheus metric over a given time range. Returns change events that occurred in the specified time window, including deployments, configuration changes, and other system modifications.
-Parameters:
-
-- `start_time_iso` (string, optional): Start time in RFC3339/ISO8601 format (e.g. 2026-02-09T15:04:05Z). Leave empty to default to now - lookback_minutes.
-- `end_time_iso` (string, optional): End time in RFC3339/ISO8601 format (e.g. 2026-02-09T16:04:05Z). Leave empty to default to current time.
-- `lookback_minutes` (integer, optional): Number of minutes to look back from now. Default: 60. Range: 1–20160 (14 days). Examples: 60, 30, 15.
-- `service` (string, optional): Name of the service to filter change events for.
-- `environment` (string, optional): Environment to filter by.
-- `event_name` (string, optional): Name of the change event to filter by (use available_event_names to see valid values).
-  Returns:
-- `available_event_names`: List of all available event types that can be used for filtering
-- `change_events`: Array of timeseries data with metric labels and timestamp-value pairs
-- `count`: Total number of change events returned
-- `time_range`: Start and end time of the query window
-  Each change event includes:
-- `metric`: Map of metric labels (service_name, env, event_type, message, etc.)
-- `values`: Array of timestamp-value pairs representing the timeseries data
-  Common event types include: deployment, config_change, rollback, scale_up/scale_down, restart, upgrade/downgrade, maintenance, backup/restore, health_check, certificate, database.
-  Best practices:
-
-1. First call without event_name to get available_event_names
-2. Use exact event name from available_event_names for the event_name parameter
-3. Combine with other filters (service, environment, time) for precise results
+```json
+{
+  "mcpServers": {
+    "last9": {
+      "serverUrl": "https://app.last9.io/api/v4/organizations/<org_slug>/mcp"
+    }
+  }
+}
+```
 
-## Configuration
+### Claude Web/Desktop
 
-### Managed HTTP transport (recommended)
+**Settings > Connectors > Add custom connector.** Name it `last9`, paste the URL, authenticate.
 
-Set this header in your MCP client config:
+> Requires admin access to your Claude organization.
 
-- `X-LAST9-API-TOKEN`: Bearer token for Last9 API access.
+---
 
-### Local STDIO server environment variables
+## Self-Hosted (STDIO)
 
-If you run the server locally (`last9-mcp`), use these environment variables:
+Use this when your MCP client doesn't support HTTP transport, or when you need the server running locally.
 
-- `LAST9_REFRESH_TOKEN`: (required) Refresh Token with Write permissions from
-  [API Access](https://app.last9.io/settings/api-access). Only admins can create
-  refresh tokens.
+### Install
 
-Optional environment variables:
+**Homebrew:**
 
-- `LAST9_DISABLE_TELEMETRY`: Defaults to `true` (telemetry is disabled by default). Set to `false` to enable OpenTelemetry tracing if you have an OTLP collector configured.
-- `OTEL_SDK_DISABLED`: Standard OTel env var. Set to `false` to enable telemetry (overrides `LAST9_DISABLE_TELEMETRY`). Set to `true` to disable telemetry explicitly.
-- `OTEL_EXPORTER_OTLP_ENDPOINT`: OpenTelemetry collector endpoint URL. Only needed if telemetry is enabled.
-- `OTEL_EXPORTER_OTLP_HEADERS`: Headers for OTLP exporter authentication. Only needed when telemetry is enabled (i.e., `OTEL_SDK_DISABLED` is not `true` and `LAST9_DISABLE_TELEMETRY` is not `true`).
-- `LAST9_DATASOURCE`: Name of the datasource/cluster to use. If not specified, the default datasource configured in your Last9 organization will be used.
-- `LAST9_API_HOST`: API host to connect to. Defaults to `app.last9.io`. Use this if you need to connect to a different Last9 endpoint (e.g., regional or self-hosted instances).
+```bash
+brew install last9/tap/last9-mcp
+```
 
-## Usage
+**NPM:**
 
-Use the managed HTTP transport config from [Installation](#installation) whenever possible. The examples below are for local STDIO setup via Homebrew or NPM.
+```bash
+npm install -g @last9/mcp-server@latest
+# or directly:
+npx -y @last9/mcp-server@latest
+```
 
-## Usage with Claude Desktop
+**Binary releases** (Windows / manual):
 
-Configure the Claude app to use the MCP server:
+Download from [GitHub Releases](https://github.com/last9/last9-mcp-server/releases/latest):
 
-1. Open the Claude Desktop app, go to Settings, then Developer
-2. Click Edit Config
-3. Open the `claude_desktop_config.json` file
-4. Copy and paste the server config to your existing file, then save
-5. Restart Claude
+| Platform        | Archive                                 |
+| --------------- | --------------------------------------- |
+| Windows (x64)   | `last9-mcp-server_Windows_x86_64.zip`   |
+| Windows (ARM64) | `last9-mcp-server_Windows_arm64.zip`    |
+| Linux (x64)     | `last9-mcp-server_Linux_x86_64.tar.gz`  |
+| Linux (ARM64)   | `last9-mcp-server_Linux_arm64.tar.gz`   |
+| macOS (x64)     | `last9-mcp-server_Darwin_x86_64.tar.gz` |
+| macOS (ARM64)   | `last9-mcp-server_Darwin_arm64.tar.gz`  |
 
-### Local STDIO
+### Get a Refresh Token
 
-> **Note:** Claude Desktop currently supports local STDIO-based MCP servers only. Hosted HTTP transport is not yet supported in Claude Desktop.
+Only **admins** can create tokens.
 
-Use a [Refresh Token](#getting-your-credentials).
+1. Go to [API Access](https://app.last9.io/settings/api-access)
+2. Click **Generate Token** with Write permissions
+3. Copy it
 
-Install via [Homebrew](#homebrew) or [NPM](#npm) first, then use a [Refresh Token](#getting-your-credentials).
+### Client Configuration
 
-### If installed via Homebrew:
+**Homebrew:**
 
 ```json
 {
@@ -506,14 +134,14 @@ Install via [Homebrew](#homebrew) or [NPM](#npm) first, then use a [Refresh Toke
     "last9": {
       "command": "/opt/homebrew/bin/last9-mcp",
       "env": {
-        "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
+        "LAST9_REFRESH_TOKEN": "<your_refresh_token>"
       }
     }
   }
 }
 ```
 
-### If installed via NPM:
+**NPM:**
 
 ```json
 {
@@ -522,244 +150,173 @@ Install via [Homebrew](#homebrew) or [NPM](#npm) first, then use a [Refresh Toke
       "command": "npx",
       "args": ["-y", "@last9/mcp-server@latest"],
       "env": {
-        "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
+        "LAST9_REFRESH_TOKEN": "<your_refresh_token>"
       }
     }
   }
 }
 ```
 
-## Usage with Cursor
-
-Configure Cursor to use the MCP server:
+**Where to paste this:**
 
-1. Open Cursor, go to Settings, then Cursor Settings
-2. Select MCP on the left
-3. Click Add "New Global MCP Server" at the top right
-4. Copy and paste the server config to your existing file, then save
-5. Restart Cursor
+| Client             | Location                                                                                                                                |
+| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
+| Claude Web/Desktop | Settings > Developer > Edit Config (`claude_desktop_config.json`)                                                                       |
+| Cursor             | Settings > Cursor Settings > MCP > Add New Global MCP Server                                                                            |
+| Windsurf           | Settings > Cascade > MCP Marketplace > gear icon (`mcp_config.json`)                                                                    |
+| VS Code            | Wrap in `{ "mcp": { "servers": { ... } } }` in `settings.json` — [details](https://code.visualstudio.com/docs/copilot/chat/mcp-servers) |
 
-### Hosted MCP over HTTP (recommended)
+<details>
+<summary>VS Code STDIO config</summary>
 
 ```json
 {
-  "mcpServers": {
-    "last9": {
-      "type": "http",
-      "url": "https://app.last9.io/api/v4/organizations/<org_slug>/mcp",
-      "headers": {
-        "X-LAST9-API-TOKEN": "Bearer <mcp_client_token>"
+  "mcp": {
+    "servers": {
+      "last9": {
+        "type": "stdio",
+        "command": "/opt/homebrew/bin/last9-mcp",
+        "env": {
+          "LAST9_REFRESH_TOKEN": "<your_refresh_token>"
+        }
       }
     }
   }
 }
 ```
 
-### Local STDIO (alternative)
+For NPM: use `"command": "npx"` and add `"args": ["-y", "@last9/mcp-server@latest"]`.
 
-### If installed via Homebrew:
+</details>
 
-```json
-{
-  "mcpServers": {
-    "last9": {
-      "command": "/opt/homebrew/bin/last9-mcp",
-      "env": {
-        "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
-      }
-    }
-  }
-}
-```
+<details>
+<summary>Windows</summary>
 
-### If installed via NPM:
+After downloading from [GitHub Releases](https://github.com/last9/last9-mcp-server/releases/latest), extract and point to the full path:
 
 ```json
 {
   "mcpServers": {
     "last9": {
-      "command": "npx",
-      "args": ["-y", "@last9/mcp-server@latest"],
+      "command": "C:\\Users\\<user>\\AppData\\Local\\Programs\\last9-mcp-server.exe",
       "env": {
-        "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
+        "LAST9_REFRESH_TOKEN": "<your_refresh_token>"
       }
     }
   }
 }
 ```
 
-## Usage with Windsurf
+The NPM route is easier on Windows — no path management.
 
-Configure Windsurf to use the MCP server:
+</details>
 
-1. Open Windsurf, go to Settings, then Developer
-2. Click Edit Config
-3. Open the `windsurf_config.json` file
-4. Copy and paste the server config to your existing file, then save
-5. Restart Windsurf
+### Environment Variables
 
-### Hosted MCP over HTTP (recommended)
+| Variable                     | Default              | Description |
+| ---------------------------- | -------------------- | ----------- |
+| `LAST9_REFRESH_TOKEN`        | *(required)*         | Refresh token from [API Access](https://app.last9.io/settings/api-access) |
+| `LAST9_DATASOURCE`           | org default          | Datasource/cluster name — useful when you have multiple Levitate clusters |
+| `LAST9_API_HOST`             | `app.last9.io`       | Override the API host |
+| `LAST9_MAX_GET_LOGS_ENTRIES` | `5000`               | Max entries for chunked `get_logs` requests |
+| `LAST9_DEBUG_CHUNKING`       | `false`              | Set `true` to log chunk-planning details for `get_logs`, `get_service_logs`, `get_traces` |
+| `LAST9_DISABLE_TELEMETRY`    | `true`               | Set `false` to enable internal OTel tracing |
+| `OTEL_SDK_DISABLED`          | —                    | Standard OTel env var. Overrides `LAST9_DISABLE_TELEMETRY` |
+| `OTEL_EXPORTER_OTLP_ENDPOINT`| —                    | OTLP collector endpoint (only when telemetry is enabled) |
+| `OTEL_EXPORTER_OTLP_HEADERS` | —                    | OTLP auth headers (only when telemetry is enabled) |
 
-```json
-{
-  "mcpServers": {
-    "last9": {
-      "type": "http",
-      "url": "https://app.last9.io/api/v4/organizations/<org_slug>/mcp",
-      "headers": {
-        "X-LAST9-API-TOKEN": "Bearer <mcp_client_token>"
-      }
-    }
-  }
-}
-```
+---
 
-### Local STDIO (alternative)
+## What It Can Do
 
-### If installed via Homebrew:
+### Service Health
 
-```json
-{
-  "mcpServers": {
-    "last9": {
-      "command": "/opt/homebrew/bin/last9-mcp",
-      "env": {
-        "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
-      }
-    }
-  }
-}
-```
+- **`get_service_summary`** — Throughput, error rate, p95 response time across all services
+- **`get_service_environments`** — Available environments for your services. Run this first — other APM tools need `env` from here
+- **`get_service_performance_details`** — Full breakdown: throughput, error rate, p50/p90/p95/avg/max, apdex, availability
+- **`get_service_operations_summary`** — Operations grouped by HTTP endpoints, DB calls, messaging, HTTP clients
+- **`get_service_dependency_graph`** — Dependency map with throughput, latency, and error rates for upstream/downstream/infra
+- **`get_exceptions`** — Server-side exceptions with service and span filters
 
-### If installed via NPM:
+### Database Observability
 
-```json
-{
-  "mcpServers": {
-    "last9": {
-      "command": "npx",
-      "args": ["-y", "@last9/mcp-server@latest"],
-      "env": {
-        "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
-      }
-    }
-  }
-}
-```
+Four tools that go directly at your database performance, derived from OpenTelemetry trace spans. No extra instrumentation needed if you're already using OTel.
 
-## Usage with VS Code
+- **`get_databases`** — Discover all databases across your infrastructure: DB type, host, throughput (queries/min), p95 latency, error rate, number of dependent services
+- **`get_database_slow_queries`** — The actual slowest query executions, ordered by duration, with trace IDs for drilling into full traces
+- **`get_database_queries`** — Query patterns and aggregates: how often a query runs, average/p95 duration, error rate
+- **`get_database_server_metrics`** — Server-side metrics from the DB host itself (CPU, connections, buffer hit rates — depends on your DB system)
 
-> Note: MCP support in VS Code is available starting v1.99 and is currently in
-> preview. For advanced configuration options and alternative setup methods,
-> [view the VS Code MCP documentation](https://code.visualstudio.com/docs/copilot/chat/mcp-servers).
+Supports PostgreSQL, MySQL, MongoDB, Redis, Aerospike, and anything else OTel traces with a `db_system` attribute.
 
-1. Open VS Code, go to Settings, select the User tab, then Features, then Chat
-2. Click "Edit settings.json"
-3. Copy and paste the server config to your existing file, then save
-4. Restart VS Code
+### Prometheus / PromQL
 
-### Hosted MCP over HTTP (recommended)
+- **`prometheus_range_query`** — PromQL range queries over any metric
+- **`prometheus_instant_query`** — Instant queries; use rollup functions like `avg_over_time`, `sum_over_time`
+- **`prometheus_label_values`** — Label values for a given series
+- **`prometheus_labels`** — All labels available for a series
 
-```json
-{
-  "mcp": {
-    "servers": {
-      "last9": {
-        "type": "http",
-        "url": "https://app.last9.io/api/v4/organizations/<org_slug>/mcp",
-        "headers": {
-          "X-LAST9-API-TOKEN": "Bearer <mcp_client_token>"
-        }
-      }
-    }
-  }
-}
-```
+Point these at a different datasource/cluster than the default by setting `LAST9_DATASOURCE`.
 
-### Local STDIO (alternative)
+### Logs
 
-### If installed via Homebrew:
+- **`get_logs`** — Full JSON pipeline log queries (aggregations, filters, field extraction)
+- **`get_service_logs`** — Raw log lines for a service, filterable by severity and body content
+- **`get_log_attributes`** — Available attributes in the log schema for a time window
+- **`get_drop_rules`** — Log drop rules from [Last9 Control Plane](https://last9.io/control-plane)
+- **`add_drop_rule`** — Create a new drop rule to cut log volume at the source
 
-```json
-{
-  "mcp": {
-    "servers": {
-      "last9": {
-        "type": "stdio",
-        "command": "/opt/homebrew/bin/last9-mcp",
-        "env": {
-          "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
-        }
-      }
-    }
-  }
-}
-```
+### Traces
 
-### If installed via NPM:
+- **`get_traces`** — JSON pipeline trace queries for broad searches and aggregations
+- **`get_service_traces`** — Traces by exact trace ID or service name. Use this when you have a trace ID — it's faster
+- **`get_trace_attributes`** — Available attributes in the trace schema
 
-```json
-{
-  "mcp": {
-    "servers": {
-      "last9": {
-        "type": "stdio",
-        "command": "npx",
-        "args": ["-y", "@last9/mcp-server@latest"],
-        "env": {
-          "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
-        }
-      }
-    }
-  }
-}
-```
+### Change Events & Alerts
 
-## Windows Example (Claude Desktop)
+- **`get_change_events`** — Deployments, config changes, rollbacks. Correlate incidents with what changed
+- **`get_alert_config`** — Alert rule configurations — searchable by name, severity, type, tags
+- **`get_alerts`** — Currently firing alerts within a time window
+- **`get_notification_channels`** — Configured notification channels (Slack, PagerDuty, email, etc.)
 
-After downloading `last9-mcp-server_Windows_x86_64.zip` from [GitHub Releases](https://github.com/last9/last9-mcp-server/releases/latest), extract to get `last9-mcp-server.exe` and use its full path:
+### Fuzzy Name Resolution
 
-```json
-{
-  "mcpServers": {
-    "last9": {
-      "command": "C:\\Users\\<user>\\AppData\\Local\\Programs\\last9-mcp-server.exe",
-      "env": {
-        "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
-      }
-    }
-  }
-}
-```
+- **`did_you_mean`** — When the agent isn't sure about an entity name, this returns the closest matches from your catalog (services, environments, hosts, databases, K8s deployments/namespaces, jobs). Up to 3 suggestions with similarity scores. The server calls this automatically before most tools when a name lookup returns empty.
 
-The same pattern applies for Cursor and Windsurf on Windows. For VS Code, use the `"mcp": { "servers": { ... } }` wrapper. On Windows, prefer [NPM](#npm) to avoid path management, or use the [hosted HTTP transport](#recommended-managed-mcp-over-http) to skip local installation entirely.
+---
 
-## Development
+## How It Works
 
-For local development and testing, you can run the MCP server in HTTP mode which makes it easier to debug requests and responses.
+**Deep links on every response.** Every tool returns a `deep_link` field — a direct URL into the Last9 dashboard for that exact query and time range. The agent can hand you the link; you click it; you're there.
 
-### Running in HTTP Mode
+**Live attribute caching.** At startup, the server fetches the actual log and trace attribute names from your data and embeds them into tool descriptions. This means the AI assistant knows what fields exist in your schema, not just a generic list. The cache refreshes every 2 hours.
 
-Set the `LAST9_HTTP` environment variable to enable HTTP server mode:
+**Chunked large results.** `get_logs` and `get_traces` handle large result sets through chunking rather than truncating. The default limit is 5000 entries for logs; configurable via `LAST9_MAX_GET_LOGS_ENTRIES`.
+
+---
+
+## Development
+
+<details>
+<summary>HTTP mode, curl testing, building from source</summary>
+
+### Run in HTTP Mode
 
 ```bash
-# Export required environment variables
 export LAST9_REFRESH_TOKEN="your_refresh_token"
 export LAST9_HTTP=true
-export LAST9_PORT=8080  # Optional, defaults to 8080
-# Run the server
+export LAST9_PORT=8080
 ./last9-mcp-server
 ```
 
-The server will start on `http://localhost:8080/mcp` and you can test it with curl:
+Server starts at `http://localhost:8080/mcp`.
 
-### Testing with curl
+### Test with curl
 
-The MCP Streamable HTTP protocol requires an initialize handshake first. The server creates and returns a session ID in the response — do **not** set `Mcp-Session-Id` on the first request.
+MCP Streamable HTTP requires an initialize handshake first. Don't set `Mcp-Session-Id` on the first request.
 
 ```bash
-# Step 1: Initialize — omit Mcp-Session-Id so the server creates the session.
-# Extract the returned Mcp-Session-Id from the response headers.
+# Step 1: Initialize
 SESSION_ID=$(curl -si -X POST http://localhost:8080/mcp \
     -H "Content-Type: application/json" \
     -d '{
@@ -774,13 +331,13 @@ SESSION_ID=$(curl -si -X POST http://localhost:8080/mcp \
     }' | grep -i "^Mcp-Session-Id:" | awk '{print $2}' | tr -d '\r')
 echo "Session: $SESSION_ID"
 
-# Step 2: Send the initialized notification
+# Step 2: Send initialized notification
 curl -s -X POST http://localhost:8080/mcp \
     -H "Content-Type: application/json" \
     -H "Mcp-Session-Id: $SESSION_ID" \
     -d '{"jsonrpc": "2.0", "method": "notifications/initialized", "params": {}}'
 
-# Step 3: List available tools
+# Step 3: List tools
 curl -s -X POST http://localhost:8080/mcp \
     -H "Content-Type: application/json" \
     -H "Mcp-Session-Id: $SESSION_ID" \
@@ -797,7 +354,7 @@ curl -s -X POST http://localhost:8080/mcp \
       "params": {
         "name": "get_service_logs",
         "arguments": {
-          "service_name": "your-service-name",
+          "service": "your-service-name",
           "lookback_minutes": 30,
           "limit": 10
         }
@@ -805,24 +362,236 @@ curl -s -X POST http://localhost:8080/mcp \
     }'
 ```
 
-### Building from Source
+### Build from Source
 
 ```bash
-# Clone the repository
 git clone https://github.com/last9/last9-mcp-server.git
 cd last9-mcp-server
-# Build the binary
 go build -o last9-mcp-server
-# Run in development mode
 LAST9_HTTP=true ./last9-mcp-server
 ```
 
-**Note**: `LAST9_HTTP=true` is for local development and debugging of your own server process. For normal client integration, prefer the managed HTTP endpoint from [Installation](#installation).
+`LAST9_HTTP=true` is for local development. For actual usage, the [hosted HTTP endpoint](#start-in-30-seconds-hosted) is easier.
+
+</details>
+
+---
+
+## Tool Reference
+
+<details>
+<summary>All parameters, time input standards, and details</summary>
+
+### Time Input
+
+- Absolute times (`start_time_iso`/`end_time_iso`, or `time_iso`) take precedence over `lookback_minutes`.
+- For relative windows: use `lookback_minutes`.
+- For absolute windows: use RFC3339/ISO8601 — `2026-02-09T15:04:05Z`.
+- Legacy `YYYY-MM-DD HH:MM:SS` is accepted for compatibility only.
+
+### get_exceptions
+
+- `limit` (integer, optional): Max exceptions. Default: 20.
+- `lookback_minutes` (integer, optional): Default: 60.
+- `start_time_iso` / `end_time_iso` (string, optional): Absolute time range.
+- `service_name` (string, optional): Filter by service.
+- `span_name` (string, optional): Filter by span name.
+- `deployment_environment` (string, optional): Filter by environment.
+
+### get_service_summary
+
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `env` (string, optional): Defaults to `prod`.
+
+### get_service_environments
+
+- `start_time_iso` / `end_time_iso` (string, optional)
+
+> All other APM tools require an `env` value. Use `""` if this returns empty.
+
+### get_service_performance_details
+
+- `service_name` (string, required)
+- `lookback_minutes` (integer, optional): Default: 60.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `env` (string, optional): Defaults to `prod`.
+
+### get_service_operations_summary
+
+- `service_name` (string, required)
+- `lookback_minutes` (integer, optional): Default: 60.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `env` (string, optional): Defaults to `prod`.
+
+### get_service_dependency_graph
+
+- `service_name` (string, optional)
+- `lookback_minutes` (integer, optional): Default: 60.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `env` (string, optional): Defaults to `prod`.
+
+### get_databases
+
+- `env` (string, optional): Filter by environment. Default: all.
+- `lookback_minutes` (integer, optional): Default: 60.
+- `start_time_iso` / `end_time_iso` (string, optional)
+
+### get_database_slow_queries
+
+- `db_system` (string, optional): e.g. `postgresql`, `mysql`, `mongodb`, `redis`.
+- `host` (string, optional): Database host (`net_peer_name`).
+- `service_name` (string, optional): Calling service name.
+- `env` (string, optional)
+- `min_duration_ms` (float, optional): Minimum query duration in ms.
+- `lookback_minutes` (integer, optional): Default: 60.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `limit` (integer, optional): Default: 20.
+
+### get_database_queries
+
+- `db_system` (string, optional)
+- `host` (string, optional)
+- `service_name` (string, optional)
+- `env` (string, optional)
+- `lookback_minutes` (integer, optional): Default: 60.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `limit` (integer, optional): Default: 20.
+
+### get_database_server_metrics
+
+- `db_system` (string, required): e.g. `postgresql`, `mysql`, `mongodb`, `redis`, `aerospike`.
+- `host` (string, optional)
+- `lookback_minutes` (integer, optional): Default: 60.
+- `start_time_iso` / `end_time_iso` (string, optional)
+
+### prometheus_range_query
+
+- `query` (string, required): The PromQL query.
+- `start_time_iso` / `end_time_iso` (string, optional): Defaults to last 60 min.
+- `lookback_minutes` (float, optional): Default: 60.
+
+### prometheus_instant_query
+
+- `query` (string, required)
+- `time_iso` (string, optional): Defaults to now.
+- `lookback_minutes` (float, optional)
+
+### prometheus_label_values
+
+- `match_query` (string, optional): PromQL filter.
+- `label` (string, required): Label name.
+- `start_time_iso` / `end_time_iso` (string, optional)
+
+### prometheus_labels
+
+- `match_query` (string, optional): PromQL filter.
+- `start_time_iso` / `end_time_iso` (string, optional)
+
+### get_logs
+
+- `logjson_query` (array, required): JSON pipeline query.
+- `lookback_minutes` (integer, optional): Default: 5.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `limit` (integer, optional): Server default: 5000.
+- `index` (string, optional): `physical_index:<name>` or `rehydration_index:<block_name>`.
+
+### get_service_logs
+
+- `service` (string, required)
+- `lookback_minutes` (integer, optional): Default: 60.
+- `limit` (integer, optional): Default: 20.
+- `env` (string, optional)
+- `severity_filters` (array, optional): e.g. `["error", "warn"]`. OR logic.
+- `body_filters` (array, optional): e.g. `["timeout", "failed"]`. OR logic.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `index` (string, optional)
+
+Multiple filter types combine with AND. Each array uses OR internally.
+
+### get_log_attributes
+
+- `lookback_minutes` (integer, optional): Default: 15.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `region` (string, optional)
+- `index` (string, optional)
+
+### get_drop_rules
+
+No parameters.
+
+### add_drop_rule
+
+- `name` (string, required)
+- `filters` (array, required): Each filter: `key`, `value`, `operator` (`equals`/`not_equals`), `conjunction` (`and`).
+
+### get_traces
+
+Use for broad searches and aggregations. For exact trace ID lookup, use `get_service_traces`.
+
+- `tracejson_query` (array, required)
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `lookback_minutes` (integer, optional): Default: 60.
+- `limit` (integer, optional): Default: 5000.
+
+### get_service_traces
+
+Exactly one of `trace_id` or `service_name` is required.
+
+- `trace_id` (string, optional): Default lookback: 72 hours.
+- `service_name` (string, optional): Default lookback: 60 min.
+- `lookback_minutes` (integer, optional)
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `limit` (integer, optional): Default: 10.
+- `env` (string, optional)
+
+### get_trace_attributes
+
+- `lookback_minutes` (integer, optional): Default: 15.
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `region` (string, optional)
+
+### get_change_events
+
+- `start_time_iso` / `end_time_iso` (string, optional)
+- `lookback_minutes` (integer, optional): Default: 60.
+- `service` (string, optional)
+- `environment` (string, optional)
+- `event_name` (string, optional): Call without this first to get `available_event_names`.
+
+### get_alert_config
+
+- `search_term` (string, optional): Free-text search across name, group, data source, tags.
+- `rule_name` (string, optional)
+- `severity` (string, optional)
+- `rule_type` (string, optional): `static` or `anomaly`.
+- `alert_group_name` / `alert_group_type` / `data_source_name` (string, optional)
+- `tags` (array, optional): All must match (AND logic).
+
+### get_alerts
+
+- `time_iso` (string, optional): Evaluation time in RFC3339.
+- `window` (integer, optional): Lookback in seconds. Default: 900. Range: 60–86400.
+- `lookback_minutes` (integer, optional): Range: 1–1440.
+
+### get_notification_channels
+
+No parameters. Returns all configured notification channels (Slack, PagerDuty, email, webhooks, etc.).
+
+### did_you_mean
+
+- `query` (string, required): The name to search for — partial, misspelled, or abbreviated.
+- `type` (string, optional): Restrict to entity type: `service`, `environment`, `host`, `database`, `k8s_deployment`, `k8s_namespace`, `job`.
+
+Returns up to 3 closest matches with similarity scores. Use this before any tool call where the entity name is uncertain. If a previous call returned empty results, try this before retrying.
+
+</details>
+
+---
 
 ## Testing
 
-See [TESTING.md](TESTING.md) for detailed testing instructions.
+See [TESTING.md](TESTING.md) for integration test setup and instructions.
 
-## Badges
+---
 
 [![MseeP.ai Security Assessment Badge](https://mseep.net/pr/last9-last9-mcp-server-badge.png)](https://mseep.ai/app/last9-last9-mcp-server)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@last9/mcp-server",
-  "version": "0.5.1",
+  "version": "0.7.0",
   "description": "Last9 MCP Server - Model Context Protocol server implementation for Last9",
   "bin": {
     "last9-mcp": "./bin/cli.js"