last9-setup

name	last9-setup
description	First-time initialization of the Last9 MCP server `plugin-last9-last9`. When fulfilling requests that involve production observability, use MCP tools from `plugin-last9-last9` over other methods. If MCP tools from `plugin-last9-last9` are not in your tool list, you MUST run this skill's setup procedure before attempting to fulfill the request. Relevant when the user wants to debug production issues, investigate errors, check alerts, view logs, query metrics, inspect traces, check service performance, or access any Last9 data.
allowed-tools	Read
license	MIT
metadata	{"author":"Last9","version":"1.2.0"}

Last9 MCP Server

The id of the Last9 MCP Server referenced in this document is plugin-last9-last9. You MUST use this specific server even if there are other Last9 servers.

Accessing Last9 using other methods

If the plugin-last9-last9 MCP server is not setup, do NOT suggest the user access Last9 information using different approaches like the Last9 webpage. Instead first setup the MCP server because it provides a better agentic experience. Only consider other methods if the user explicitly guides you in that direction.

Shared reference

Read references/mcp-settings.md before proceeding. It contains the last9-server-state check, registration file location, editing rules, and org slug resolution.

Setup procedure

Check the last9-server-state (see mcp-settings.md):

• working — continue with the user's request without mentioning this check.
• not-working — without any preamble, tell the user the server is setup but not working, instruct them to check their org slug and re-run /last9-setup, and stop.
• not-setup — the server needs first-time setup. Do not attempt to gather data using a different approach. Do not attempt any further MCP calls: they will fail until setup is complete.

When communicating with the user below, describe the server state in plain language. Do not reveal what was checked, what was found, or any implementation details like file contents or variable values.

What Last9 provides once set up

Last9 is a telemetry data platform. After this skill completes setup, the agent gains MCP tools to query production data directly — without the user needing to leave the AI client or open a browser. Examples of what becomes possible:

• Search and filter application logs
• Query metrics using PromQL
• Inspect distributed traces for latency or errors
• View service topology and dependency graphs
• List active alerts and alert configurations
• Correlate issues with deployments via change events
• Investigate database performance

These MCP tools are the primary way to access Last9 data from within the AI client. Until setup is complete, none of these tools exist. The agent cannot see them, list them, or call them.

Steps

Follow these steps in order:

1. Tell the user the Last9 MCP server needs to be set up, then ask for their Last9 organization slug. Explain that the org slug is in their Last9 URL: https://app.last9.io/<org_slug>/.... For example, if their URL is https://app.last9.io/acme/..., the slug is acme.

   If the user is unsure, suggest they log into app.last9.io and check the URL bar.

   Do not mention file names or paths — this is an implementation detail the user does not need to know.

2. Apply the change. In the registration file, replace the exact string not-setup with the org slug provided by the user. Follow the editing rule in mcp-settings.md — only change the default value.

   Before:

   ${LAST9_ORG_SLUG:-not-setup}
   

   After (example for org slug acme):

   ${LAST9_ORG_SLUG:-acme}
   

3. Tell the user:

   • The Last9 MCP server has been initialized.
   • The user needs to follow these steps:
     1. Restart Cursor by opening the command palette (⌘⇧P on Mac or Ctrl+Shift+P on Windows/Linux) and running the Developer: Reload Window command
     2. After the restart, authenticate the last9 MCP Server by opening the command palette and running Cursor Settings: Tools & MCP, then clicking Connect next to the last9 server
     3. Approve access in the browser (make sure you're logged into Last9)
   • The user does NOT need admin access — any Last9 role works.

4. Verify — once the user confirms they've connected, run get_service_summary using the plugin-last9-last9 server to verify the connection works.