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. Returns name, slug, version, and timestamps for each dashboard. 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

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.

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

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

Get the details about the 10 most recent exceptions matching a source file path.

query_find_exceptions_in_file

Run an arbitrary SQL SELECT query against the Logfire database for investigation and exploration. The engine is Apache DataFusion (Postgres-like syntax). Use this tool to explore data freely when none of the more targeted tools fit your need. The queryable tables are `records`, `metrics`, `alerts_ext`, `alert_runs_ext`, `alert_issues_ext`, `filter_alert_issue_hits_ext`, and `saved_searches_ext`; use these exact names, there are no other tables. Cross-source joins are supported (e.g. join `alert_issues_ext` to `records` via `trace_id`). This is a read-only interface: only SELECT queries are supported. Do not attempt DELETE, UPDATE, INSERT, ALTER, DROP, CREATE, or other DDL/DML statements. Use the SQL reference already provided in your instructions when it covers the query. Call `query_schema_reference` only for missing schema or SQL guidance, or to diagnose a column or type error. Its availability does not require a lookup before every query. `query_schema_reference` is a tool, never a table.

query_run

Get the database schema and query handbook for the Logfire DataFusion database. Returns SQL `CREATE TABLE` statements for all queryable tables (`records`, `metrics`, `alerts_ext`, `alert_runs_ext`, `alert_issues_ext`, `filter_alert_issue_hits_ext`, and `saved_searches_ext`) together with a handbook of guidance for writing efficient queries. The SQL dialect is Postgres-like (Apache DataFusion engine). Call this when the SQL reference in your instructions does not cover the columns, tables, or query syntax you need, or to diagnose a schema-related query error. Reuse schema guidance you already have instead of calling this before every `query_run`.

query_schema_reference

Create a new schedule for gating alert notification delivery to specific time windows.

schedule_create

Permanently delete a schedule. Alert-channel pairs using this schedule will revert to always-deliver.

schedule_delete

Get a specific schedule by ID.

schedule_get