# Run Bird from Droid

Droid has no plugin format, so the skills are files you copy in. Everything after that is the same two steps, and what you get is an agent that can roll a signing secret across every environment and tell you which one still holds the old one.

## One copy, one line, then a sign-in

This is the one client where the skills step is manual. It is a single cp, and saying so is better than a setup that quietly does not work.

**terminal**

```bash
$ git clone https://github.com/messagebird/bird-ai
$ cp -r bird-ai/plugins/bird/skills/. .factory/skills/

# both skills land: bird-cli and email-audit
```

**terminal**

```bash
$ droid mcp add bird https://mcp.bird.com --type http
```

**inside droid**

/mcp → bird → Sign in

- Before: not signed in
- After: ready

Finish the browser sign-in from the server manager. Until then the tools are listed and every call fails with a 401.

## What Droid already knows. Three operations, and the traps that would otherwise cost it a few rounds of --help.

- Send a message. Send it, then read it back, because accepted is not the same as arrived.
- Set up a sender. Create the domain, add the DNS records it hands you, then verify. Not immediately: DNS takes its time.
- Get notified of events. Tell Bird where to send them, then test that they land. Keep the signing secret from the create call, because it is never shown again.

### What to ask for

- Roll the webhook signing secret across staging and production.
- List every webhook endpoint, grouped by environment.
- Replay the deliveries that failed against my endpoint.
- Check every sending domain is verified before the cutover.
- Which workspace and region am I acting as right now?