> ## Documentation Index
> Fetch the complete documentation index at: https://docs.warrn.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Give Warrnagen access to external tools via MCP connectors.

## Overview

Connectors let Warrnagen — Warrn's AI agent — interact with external tools during incident investigation and response. Each connector exposes a set of tools that Warrnagen can call, with configurable access levels per tool.

Connectors use the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) to communicate with external services.

## Available Connectors

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/connectors/github">
    Access repositories, issues, pull requests, and code search.
  </Card>

  <Card title="Grafana" icon="chart-line" href="/connectors/grafana">
    Query dashboards, alerts, and metrics for observability.
  </Card>

  <Card title="Coralogix" icon="magnifying-glass-chart" href="/connectors/coralogix">
    Search logs, traces, and alerts across your stack.
  </Card>

  <Card title="Custom MCP" icon="server" href="/connectors/custom-mcp">
    Connect any MCP-compatible server.
  </Card>
</CardGroup>

## How Connectors Work

1. **Install** a connector from **Settings → Connectors**.
2. **Authenticate** — provide API keys, or link to an existing integration (e.g., GitHub OAuth).
3. **Configure tool access** — set each tool to Allow, Needs Approval, or Blocked.
4. **Bind to services** — optionally map connector resources (repos, dashboards) to Warrn services.

```mermaid theme={null}
flowchart LR
  warrnagen["Warrnagen"] --> connector["Connector (MCP)"]
  connector --> external["External Tool"]
  external --> connector
  connector --> warrnagen
```

## Tool Access Levels

Each tool exposed by a connector can be set to one of three access levels:

| Level              | Behavior                                                                |
| ------------------ | ----------------------------------------------------------------------- |
| **Allow**          | Warrnagen can call this tool automatically during investigations.       |
| **Needs Approval** | Warrnagen must request approval before calling. Default for most tools. |
| **Blocked**        | Tool is completely disabled.                                            |

## Service Bindings

Bindings map connector resources to Warrn services. For example, you can bind a GitHub repository to a service so Warrnagen knows which repo to search when investigating alerts for that service.

## Custom MCP Servers

You can connect any MCP-compatible server by providing its URL. This lets you integrate internal tools, custom APIs, or any service that implements the MCP protocol.

## Best Practices

1. Start with **Needs Approval** for write operations — let the team build trust before allowing autonomous writes.
2. Bind connectors to services so Warrnagen has the right context during investigations.
3. Use the built-in connectors when available — they handle auth and tool discovery automatically.
4. Review tool access levels periodically as your team's comfort with AI automation evolves.