agy-discord-mcp

Discord bridge and MCP tools for the agy (Antigravity) CLI. It connects a Discord bot to agy in two ways:

• bot relay — inbound Discord messages are sent to agy --print and agy's reply is posted back (text only).

• mcp mode — exposes Discord tools (reply, send_message with file attachments, react, fetch history, download attachments, …) to an interactive agy session over stdio, so agy can talk to Discord itself — including posting generated images.

It is a sibling of codex-discord-mcp, ported to agy. Because agy --print writes a clean response straight to stdout (no JSON to parse) and agy saves generated images as real files on disk, the bridge is a little simpler than the Codex original.

Requirements

• Node.js >= 20

• The agy (Antigravity) CLI installed and authenticated (check with agy --version)

• A Discord bot token (with the Message Content intent enabled)

Related MCP server: discord-mcp-agent

Install

npm install -g agy-discord-mcp
agy-discord-mcp doctor

Or run it without a global install:

npx agy-discord-mcp@latest doctor

For local development from this repository:

npm ci
npm run build
npm link

Configure

Store your Discord bot token (written to ~/.agy/discord/.env, mode 600):

agy-discord-mcp configure <bot-token>
# or interactively:
agy-discord-mcp init

Invite the bot and check local status:

agy-discord-mcp invite-url <discord-client-id>
agy-discord-mcp doctor

Access control

Inbound access is allowlist/pairing based and managed only from the CLI — never from Discord messages:

agy-discord-mcp access show
agy-discord-mcp access policy <pairing|allowlist|disabled>
agy-discord-mcp access allow-user <discord-user-id>
agy-discord-mcp access allow-channel <channel-id> [--no-mention] [--allow-user <id>...]
agy-discord-mcp access pair <code>      # approve a DM pairing code

Under the default pairing policy, the first DM from an unknown user returns a one-time code; run access pair <code> on the host to approve them.

bot relay mode

agy-discord-mcp bot

Each allowed message becomes agy --print "<prompt>" run in AGY_WORKDIR, and the trimmed stdout is posted back. Set AGY_RESUME_BY_CHANNEL=true to keep a per-channel agy conversation (resumed via --conversation <id>, detected from agy's conversations directory).

Files come back in relay mode too — not just images. The relay adds the output dir (default ~/agy_images, set by AGY_DISCORD_GENERATED_IMAGES_DIR) to agy's workspace and tells agy to save any user-facing file there; any deliverable agy writes during the turn — images plus common document/data/archive types (md, html, pdf, csv, json, zip, docx, …; code/temp files are ignored) — is detected and attached to the Discord reply automatically (≤25 MB each, up to 10). This needs no MCP server. If other agy workloads also write to ~/agy_images (e.g. image-gen crons), point the bot at a dedicated dir via AGY_DISCORD_GENERATED_IMAGES_DIR so their output isn't picked up.

agy is launched through its wrapper, which auto-injects --dangerously-skip-permissions — every tool call is auto-approved. Treat Discord input as untrusted: run in an isolated workspace, set AGY_SANDBOX=1, or acknowledge the risk with AGY_DISCORD_ASSUME_YES=true.

mcp mode (agy drives Discord)

Caveat (current agy): registering an MCP server in agy's settings makes a headless agy --print hang on a first-use, interactive "trust this MCP server?" prompt — there is no config key (the mcpServers schema has no trust field) or agy mcp subcommand to pre-approve it. Since that global setting is read by every agy invocation, it also breaks the relay's own agy --print calls and any other headless agy users. Enable this only for a dedicated interactive agy session that can answer the prompt; for normal use prefer relay mode above, which already attaches images.

Register the MCP server by merging a mcpServers block into ~/.gemini/settings.json (or ~/.gemini/antigravity-cli/settings.json). Generate it with:

agy-discord-mcp print-config        # node + absolute path form
agy-discord-mcp print-config --npx  # npx form

Example (agy-mcp-config.example.json):

{
  "mcpServers": {
    "discord": {
      "command": "node",
      "args": ["/path/to/agy-discord-mcp/dist/cli.js", "mcp"],
      "timeout": 60000,
      "trust": true
    }
  }
}

Then run agy normally; it can call the Discord tools below. Inbound Discord messages are queued — poll with list_pending_messages, reply, then mark_message_handled.

Sending images / files

agy writes generated images as real files (its native generate_image tool, or the agy-image skill, save to a path you choose — default ~/agy_images). Pass that absolute path in the files array of reply/send_message. Files must live under an allowed attachment root (see AGY_DISCORD_ATTACHMENT_ROOTS); the agy image dir and the bridge inbox are always allowed.

Tools

Environment

Development

npm run typecheck
npm test
npm run build
npm run dev:bot   # tsx src/cli.ts bot
npm run dev:mcp   # tsx src/cli.ts mcp

Publishing

GitHub Releases publish to npm through .github/workflows/release.yml.

1. Make sure npm trusted publishing is configured for Openclaw-Metis/agy-discord-mcp and the release.yml workflow.

2. Bump package.json and package-lock.json to the release version and commit the change.

3. Create a GitHub Release whose tag is v plus the package version, for example v0.1.0.

The release workflow checks that the tag matches package.json, runs typecheck, tests, and build, then publishes to npm with provenance. Normal releases use the npm latest dist-tag; GitHub pre-releases use next.

License

MIT