Logfire

Update a webhook channel's URL, format, label, or active status. Only provided fields are changed.

channel_update_webhook

Add a new panel to an existing dashboard with optional layout position.

dashboard_add_panel

Add a single variable to a dashboard at an optional position.

dashboard_add_variable

Create a new dashboard from a Perses JSON definition or as an empty dashboard.

dashboard_create

Create a new layout group in a dashboard. Groups organize panels into collapsible sections.

dashboard_create_group

Delete a dashboard by slug. This permanently removes the dashboard and all its panels.

dashboard_delete

Delete an empty layout group from a dashboard. Fails if the group still contains panels; remove panels first. The response confirms success; no need to call dashboard_get to verify.

dashboard_delete_group

Get the full dashboard definition as Perses-compatible JSON. Also suitable for exporting or version-controlling dashboards.

dashboard_get

List dashboards in a project with optional search and cursor-based pagination. Each dashboard has `id`, `dashboard_name`, `dashboard_slug`, `version`, and timestamps. Returns an empty list if no dashboards exist; do not retry if the list is empty. Use the `search` parameter to filter by name.

dashboard_list

Get the panel guide and the JSON schema of every panel kind's settings. Covers which query each kind takes, how query columns become series and labels, layout rules, and common mistakes. Call once before creating or restyling panels.

dashboard_panel_reference

Remove a panel from a dashboard. This also removes associated layout items. The response confirms success; no need to call dashboard_get to verify.

dashboard_remove_panel

Remove a variable from a dashboard by name. The response confirms success; no need to call dashboard_get to verify.

dashboard_remove_variable

Change the title of a dashboard layout group.

dashboard_rename_group

Change the display order of layout groups in a dashboard.

dashboard_reorder_groups

Set whether a dashboard layout group is collapsed or expanded.

dashboard_toggle_group_collapse

Update dashboard time range and auto-refresh settings. For renaming or replacing the full definition, use dashboard_update. For individual panels, use dashboard_update_panel

dashboard_update_settings

Return the AI-agent prompt to instrument an AI agent so it appears on the Agents page. Gives the exact instructions for emitting the OpenTelemetry GenAI `invoke_agent` / `gen_ai.agent.name` spans Logfire's Agents page needs. The prompt is project-agnostic: it only embeds this Logfire instance's base URL (so self-hosted deployments get their own endpoint), so this tool needs no project and never asks for a token.

get_agents_setup_prompt

Return the AI-agent prompt to set up runtime feature flags with Logfire managed variables. Gives the exact, project-scoped instructions for converting hard-coded values / env toggles into `logfire.var(...)` managed variables that change live from the UI or MCP. Follow the returned prompt; the SDK reads a `project:read_variables` key from `LOGFIRE_API_KEY`, which the user supplies out of band, so this tool never asks for the key.

get_feature_flags_setup_prompt

Return the AI-agent prompt to set up infrastructure monitoring with Logfire. Gives the exact, project-scoped instructions for running an OpenTelemetry Collector that ships this surface's telemetry to Logfire and confirming it arrives. Follow the returned prompt; it references `${env:LOGFIRE_TOKEN}` and never asks for the token.

get_infrastructure_setup_prompt

Return the AI-agent prompt to instrument this application with the Logfire SDK. Gives the exact, project-scoped instructions for adding Logfire/OpenTelemetry to the codebase and confirming telemetry arrives. Follow the returned prompt; it reads the write token from the `LOGFIRE_TOKEN` env var and never asks for the token.

get_instrumentation_setup_prompt

Install an integration into a project, enabling its standard dashboards and creating its alerts. Recommended-tier alerts install active; diagnostic-tier alerts install inactive (opt-in). All alerts install without a notification channel: add one to get notified. Idempotent: installing an already-installed integration refreshes its recorded version, re-enables the same standard dashboards, and skips alerts that already exist. Use `list_integrations` first to find valid integration ids.

integration_install

List the Integrations catalog with this project's install/detection state. Returns one entry per available integration (e.g. Redis), including whether it is `installed`, whether its telemetry has been `detected` in the project, the catalog `version`, and how many dashboards and alerts it bundles. An integration that is still in preview is listed only when this project has installed it.

integration_list

Get a single tracked exception issue by its number, including the stacktrace. The issue number is the integer shown in the UI and in issue URLs (`.../[organization]/[project]/issues/[issue_number]`), so this resolves a shared issue link to full detail - including `first_exception_stacktrace` - in one call.

issue_get

List tracked exception issues for a project with cursor-based pagination. Returns issues (exceptions grouped by fingerprint) plus a `next_cursor` that callers pass back to fetch the following page. `next_cursor` is `None` when no further pages exist. Returns an empty list if issues are not enabled for the project.

issue_list

Open, ignore, or resolve one or more exception issues. Use this when asked to ignore, dismiss, resolve, close, or reopen issues. Returns the updated issues.

issue_set_states

Set up a local development session for sending telemetry to Logfire. Creates a 'dev' project (if needed), generates a write token, and returns environment variables to configure the Logfire or OpenTelemetry SDK. All telemetry is sent to the **dev** project. Use the Logfire UI or MCP query tools to view traces in this project.

local_dev_session

Create a new notification window that limits alert notification delivery to specific times.

notification_window_create

Permanently delete a notification window. Alert-channel pairs using it will revert to always-deliver.

notification_window_delete

Get a specific notification window by ID.

notification_window_get

List all notification windows in the organization. A notification window defines the times when alert notifications are delivered. Notifications outside the window are suppressed (dropped, not deferred).

notification_window_list

List all readable projects for the authenticated user in their organization.

project_list

Generate a Logfire UI link to view a specific trace. Returns a URL that opens the Logfire dashboard filtered to show the specified trace. The link includes `since` and `until` parameters when the trace timestamp lookup succeeds, helping the UI load the correct time range. If that optional lookup is unavailable, the returned trace-filter link still works without time hints.

project_logfire_link

Generate a Logfire project UI link for live-view/filter pages. Returns a URL for the project-level Logfire UI, optionally with `q`, `since`, and `until` parameters. Use `wizard_return=True` for the CLI wizard's browser return, which records a distinct project visit before Live View. Use `handoff=True` to bootstrap a browser session from MCP OAuth when opening the URL immediately. It cannot be combined with `wizard_return=True`.

project_logfire_ui_link

Get a prompt by slug. Use the response's `variable_name` property with the `variable_*` tools to manage versions, labels, rollout, and `template_inputs_schema`.

prompt_get

Get a prompt's playground settings (mutable, shared across versions).

prompt_get_settings

Get a specific template version, including the raw `template` body.

prompt_get_version

List prompts in a project. Prompts also appear in `variable_list` as prompt-backed variables; use these `prompt_*` tools to edit their template and settings.

prompt_list

List a prompt's template versions, ordered by version number.

prompt_list_versions

Render a saved prompt without calling the model. Expands `@{...}@` composition references against live managed-variable values and fills `{{...}}` Handlebars placeholders from `inputs` (overlaid on the default scenario's saved inputs), spending no model tokens. Use it to confirm a template resolves as expected while authoring over MCP. Model execution (`prompt_run`) stays off the MCP surface.

prompt_preview

Inspect up to three exception records in one trace, without fetching the whole trace or its attributes. Prefer this tool before writing SQL for an exception investigation. Supply the trace ID and a window of at most 24 hours around its timestamp. Stack traces contain at most the last 6,000 characters and 60 lines. Messages and other fields are also excerpts, not complete values. Use `read_repository_source_context` for a frame's file and line when repository tools are available. Resolve deployed paths with `find_repository_files` first. Repository paths start at the repository root. Use `query_run` only when the excerpts omit evidence needed for the task.

query_exception_context