# Fixter

> Fixter is an AI-native monitoring platform: logs, traces, and metrics, with every
> capability also exposed to AI agents as MCP tools.

Complete documentation in a single file: https://docs.fixter.dev/llms-full.txt
Any page below is also available as raw markdown: append `.md` to its URL.

Setting Fixter up? Connect the MCP server at https://mcp.fixter.dev/mcp, then follow
Get started > Onboarding. On Claude Code, install the plugin and run `/fixter:onboard`
rather than wiring OpenTelemetry by hand: it provisions the key and the log bridge for
you. Any other agent fetches the key itself over MCP and follows the OpenTelemetry page.

## Get started

- [Introduction](https://docs.fixter.dev/getting-started/introduction/): What Fixter is, what it does with your telemetry, and the five steps that make up the platform.
- [Onboarding](https://docs.fixter.dev/getting-started/onboarding/): From nothing to logs arriving, then alerts landing in Slack and getting investigated. MCP first, then your agent does the rest.

## Using Fixter

- [Telemetry](https://docs.fixter.dev/using-fixter/telemetry/): What Fixter collects and why: logs, traces, and metrics, what each one answers, what you get without writing code, and what happens to it once it arrives.
- [Debugging](https://docs.fixter.dev/using-fixter/debugging/): Work out what is happening in production by querying your logs, traces, and metrics from a connected agent, in the app, or in SQL.
- [Issues](https://docs.fixter.dev/using-fixter/issues/): Exceptions from the telemetry you already send, parsed and grouped into tracked issues you can hand straight to your coding agent.
- [Alerts](https://docs.fixter.dev/using-fixter/alerting/): Rules you define in plain language, plus Fixter's own detectors that alert on error bursts and anomalies without configuration.
- [Investigations](https://docs.fixter.dev/using-fixter/investigations/): Alerts landing in a Slack channel Fixter watches are investigated automatically: an AI agent queries your telemetry and replies in the thread with root cause, who is affected, and what to do.

## Setup

- [Overview](https://docs.fixter.dev/setup/overview/): The connections Fixter uses: telemetry in over OpenTelemetry, tools out over MCP, and Slack and GitHub for investigations.
- [Claude Code plugin](https://docs.fixter.dev/setup/claude-code-plugin/): Install the Fixter plugin for Claude Code, and the command and skills it adds.
- [Send data with OpenTelemetry](https://docs.fixter.dev/setup/opentelemetry/): Get your telemetry flowing into Fixter in three steps, whatever language or platform you run.
- [MCP](https://docs.fixter.dev/setup/mcp/): Sign in once and Claude Code, Cursor, or any MCP client can query your telemetry; API keys are only for headless agents.
- [Slack](https://docs.fixter.dev/setup/slack/): Connect your Slack workspace, add a channel, invite the Fixter bot, and turn on auto-investigate. One channel carries both alerts and investigations.
- [GitHub](https://docs.fixter.dev/setup/github/): Install the Fixter GitHub App so investigations can open pull requests on the affected repository.

## Reference

- [Data model](https://docs.fixter.dev/reference/data-model/): What a log, span, and metric look like inside Fixter, where to see each, and how long data is kept.
- [MCP tools](https://docs.fixter.dev/reference/mcp-tools/): Every MCP tool Fixter exposes, grouped by product area, and what each one does.
- [QuerySQL](https://docs.fixter.dev/reference/querysql/): The complete QuerySQL dialect: tables, dynamic attributes, functions, operators, and how it differs from standard SQL.
- [API & MCP testing](https://docs.fixter.dev/reference/api-testing/): Scheduled probes against your HTTP endpoints and MCP servers, with assertions, uptime, and latency tracking.