# Integrations and notifications

Connect GitHub, Linear, Jira, Sentry, Slack and more as MCP integrations, set the project's GitHub account, and get notified - in the app or on Telegram.

## Integrations

Integrations give the agent tools and context: issues from Linear or Jira, errors from Sentry, messages in Slack, your GitHub. They are MCP servers, and every call the agent makes to one goes through your rules like any other tool call.

- **For one project**: the project's **Integrations** tab. A project connection is switched on only for that project.
- **For everywhere**: **Library → Extensions**.

The catalogue opens on **Recommended**, picked from your repository's files and git remote, with **Browse all** grouped by category and a search. **Nothing to paste** filters to integrations you can connect without copying a token.

Warden uses the easiest sign-in each integration supports: a browser sign-in first, then reusing a CLI you are already logged in to (GitHub reuses `gh`), then a token as a last resort.

Your own MCP servers and skills work too: once connected in Warden, they are handed to the agent, whichever agent you use.

### Rules for integrations

```yaml
default: allow
rules:
  - ask: { mcp.tool: ["*delete*", "*drop*"] }
    reason: "Destructive tool calls need a person"
  - deny: { mcp.server: slack }
    when: { trigger_mode: automated }
    reason: "Unattended runs don't post to Slack"
```

### The project's GitHub account

The Integrations tab also sets which GitHub account the project uses. Warden's pull request views, the Software Factory and the agent's own `gh` calls all use it, so work and personal accounts stay apart.

## Notifications

The bell in Mission Control is your **inbox**: chats that finished or are waiting on you, approvals, automation results, Software Factory events, and GitHub activity (review requests, mentions, assignments, new comments, CI). What you have seen and dismissed is remembered.

## Telegram

Get Warden's notifications on your phone, and answer from there, through your own Telegram bot.

:::steps
1. In Telegram, open **@BotFather**, send `/newbot`, and copy the token it gives you.
2. In Warden, open **Settings → Notifications**, paste the token (it is stored encrypted on your Mac), then open your bot and tap **Start** to pair.
3. Pick what to send: *A chat needs you*, *A chat finished*, *Blocked by policy*, *Held for review*, *Automation results*, *Software Factory*, *GitHub*.
:::

Options: **Only when I'm away from Warden**, **Answer from Telegram** (your reply goes back into the chat), **Approve from Telegram** (*Allow once* or *Deny* a policy ask), **Agents can message me and ask me questions**, and **Start new chats from Telegram** (`/new`, `/projects`). Warden sends at most 30 messages in 10 minutes.

On Warden Team, Telegram is off unless your company turns it on.