Skip to main content
Glama
codex-discord-mcp

codex-discord-mcp

codex-discord-mcp

CI

A local-first Discord bridge for Codex CLI.

Use it in three ways:

  1. Discord -> Codex: mention or DM your bot, run codex exec --json, and post the final answer back to Discord.

  2. Codex -> Discord: expose Discord tools to Codex through MCP, including reply, fetch_messages, react, edit_message, download_attachment, latest_generated_images, and recover_generated_image.

  3. Hybrid workflow: receive Discord messages into a local queue, then let Codex inspect and respond through MCP tools.

This is not an official OpenAI plugin. It is a local bridge designed around Codex CLI, MCP, and Discord bot APIs.

Which Mode Should I Use?

Goal

Use

DM Codex from Discord

bot mode

Let Codex send Discord replies

mcp mode

Let Codex read recent Discord messages

mcp mode

Queue Discord messages for Codex to inspect

mcp mode with list_pending_messages

Fully automatic Discord -> Codex -> Discord

bot mode

Related MCP server: codex-from-chatgpt

Security Model

This bridge treats Discord as untrusted input.

Discord users cannot:

  • approve pairings

  • allow users

  • allow channels

  • change bridge policy

  • read bridge state files

  • bypass Codex sandbox or approval settings

Only local terminal commands can change access policy. MCP tools can read and reply through allowlisted Discord channels, but they cannot modify the allowlist or approve pairings.

Default safety posture:

  • Default sandbox: read-only

  • Default approval policy: never, because bot mode is non-interactive

  • Recommended first run: read-only

  • Use workspace-write only in an isolated repository or disposable worktree

  • Never use danger-full-access for a public Discord channel

When bot mode starts with CODEX_SANDBOX=workspace-write or CODEX_SANDBOX=danger-full-access and CODEX_APPROVAL_POLICY=never, the bridge prints a runtime warning. Set CODEX_DISCORD_ASSUME_YES=true to suppress the warning in controlled automation.

Requirements

  • Node.js 20 or newer.

  • Codex CLI installed and authenticated for bot mode.

  • A Discord application with a bot token.

  • Discord bot privileged Message Content Intent enabled.

Install

Global install:

npm install -g codex-discord-mcp
codex-discord-mcp doctor
codex-discord-mcp init

Run through npx without a global install:

npx -y codex-discord-mcp doctor

Local development install:

npm install
npm run build
node ./dist/cli.js --help

Discord Bot Setup

  1. Create a Discord application in the Discord Developer Portal.

  2. Add a bot and copy its token.

  3. Enable Message Content Intent for the bot.

  4. Invite the bot to a server if you want guild channels.

Useful bot permissions:

  • View Channels

  • Send Messages

  • Send Messages in Threads

  • Read Message History

  • Attach Files

  • Add Reactions

Print an invite URL:

codex-discord-mcp invite-url <client-id>

Store the token locally:

codex-discord-mcp configure

The token is written to ~/.codex/discord/.env by default. Override the state directory with CODEX_DISCORD_STATE_DIR.

You can also read the token from an existing environment variable:

codex-discord-mcp configure --token-env DISCORD_BOT_TOKEN

Quick Start

Interactive setup:

codex-discord-mcp init

Check local configuration:

codex-discord-mcp doctor
codex-discord-mcp doctor --json

Mode 1: Discord To Codex Relay

Run:

codex-discord-mcp bot

Default behavior:

  • Unknown DM users receive a one-hour pairing code.

  • Pair locally with codex-discord-mcp access pair <code>.

  • After pairing, each DM message triggers codex exec --json.

  • The final Codex message is posted as a Discord reply.

  • Files the run produced are attached to that reply automatically (see below).

Useful environment variables:

export CODEX_WORKDIR="/path/to/repo"
export CODEX_SANDBOX="read-only"
export CODEX_APPROVAL_POLICY="never"
export CODEX_RESUME_BY_CHANNEL="true"
codex-discord-mcp bot

For unattended relay mode, keep CODEX_APPROVAL_POLICY=never and use the least permissive sandbox that fits the channel.

Relay File Delivery

bot mode delivers files, not just text, on by default (CODEX_DISCORD_RELAY_ATTACHMENTS=false disables both paths):

  • Generated images. Codex's built-in image_gen usually writes no file to disk; the image survives only as base64 inside the session rollout. The relay records the rollout size before each run and, after the run, decodes any image_generation_call results appended past that offset — so it attaches exactly the images this run generated, even on long resumed threads, without re-reading the whole rollout.

  • Outbox deliverables. The prompt tells Codex to save user-facing files under a per-channel outbox directory (CODEX_DISCORD_OUTBOX_DIR, default ~/.codex/discord_outbox/<channel-id>/). Document, data, archive, and media files written there during the run are attached to the reply; code files, logs, and dotfiles are ignored.

Attachments respect Discord limits: at most 10 files per reply, 25MB each. If attaching fails, the relay retries text-only so the answer itself is never lost.

Files the user attaches to a Discord message are downloaded into the bridge inbox before the run (CODEX_DISCORD_RELAY_DOWNLOAD_ATTACHMENTS=false disables this), and the prompt lists each one's local path so Codex can read it directly. Inbox files older than 7 days are pruned.

Relay Commands

Send one of these as the whole message (in mention-gated channels, @bot !status works too). They are answered immediately, even while a long run is busy:

Command

Effect

!status

What is running, for how long, how many messages are queued, and which thread the channel resumes

!stop

Cancel the running Codex task (SIGTERM, then SIGKILL) and drop queued messages

!new

Forget the channel's resumed thread so the next message starts a fresh conversation (CODEX_RESUME_BY_CHANNEL=true)

!help

List the commands

/status, /stop, /new, /help, and the aliases !cancel / !reset work the same way. Runs in one channel are serial; a message that arrives while a run is busy gets a ⏳ reaction until its turn starts.

Restarts

On shutdown the relay cancels in-flight runs instead of orphaning them, and leaves those messages pending. On the next start, pending messages received within CODEX_DISCORD_REPLAY_MAX_AGE_MS (default one hour) are replayed; older ones are marked handled and skipped, so a crash never re-runs a stale request hours later.

While a relay is running, mcp mode servers sharing the same state directory (the interactive Codex, or the one Codex starts inside each relay run) leave inbound handling to the relay: they keep serving outbound tools but stop duplicating typing indicators, ack reactions, pairing replies, and queue writes.

Mode 2: Codex MCP Tools

Print a local config snippet:

codex-discord-mcp print-config

Print an npx based config snippet:

codex-discord-mcp print-config --npx

Add the snippet to ~/.codex/config.toml or a trusted project .codex/config.toml. A typical npx config looks like:

[mcp_servers.discord]
command = "npx"
args = ["-y", "codex-discord-mcp", "mcp"]
startup_timeout_sec = 20
tool_timeout_sec = 60

Then start Codex and run /mcp to confirm the Discord tools are loaded.

Available MCP tools:

Tool

Risk

Notes

fetch_messages

Low

Reads recent allowlisted channel history

list_pending_messages

Low

Reads local queue entries

bridge_status

Low

Reads local bridge status

react

Low

Adds a reaction

reply

Medium

Sends a Discord message

send_message

Medium

Sends a Discord message

edit_message

Medium

Edits a message previously sent by the bot

download_attachment

Medium

Downloads Discord attachments into the local inbox

latest_generated_images

Low

Returns absolute paths of the newest images from Codex's image_gen output dir

recover_generated_image

Medium

Decodes the most recent image_gen image from the Codex session rollout and writes it to disk

mark_message_handled

Medium

Mutates local queue state

Access Control

Access is managed by local CLI commands, not MCP tools.

codex-discord-mcp access show
codex-discord-mcp access policy allowlist
codex-discord-mcp access allow-user 123456789012345678
codex-discord-mcp access allow-channel 234567890123456789
codex-discord-mcp access allow-channel 234567890123456789 --no-mention

DM policy values:

  • pairing: unknown DM users get a one-hour pairing code. This is the default.

  • allowlist: unknown DM users are silently ignored.

  • disabled: all DMs are ignored.

Guild channels are opt-in by channel ID. By default, the bot only responds in an allowed guild channel when it is mentioned or when the user replies to a recent bot message. Use --no-mention only for dedicated bot channels.

Attachment Safety

The bridge refuses to attach its own state files, except files downloaded into the inbox. It also blocks attachment paths outside the configured attachment roots.

Attachment uploads are restricted by default to:

  • the bridge process working directory

  • CODEX_WORKDIR

  • the bridge inbox

  • Codex's built-in image_gen output directory (~/.codex/generated_images, or CODEX_DISCORD_GENERATED_IMAGES_DIR)

  • the relay outbox (~/.codex/discord_outbox, or CODEX_DISCORD_OUTBOX_DIR)

The image_gen output directory is always allowed so generated images can be attached. Codex's built-in image_gen shows an inline preview but often writes no file to disk — in that case call recover_generated_image, which decodes the just-generated image from the active session rollout and saves it to the image_gen output dir, returning the absolute path. (latest_generated_images lists already-saved image files.) Then pass the path in the files array of reply/send_message.

To allow generated files from other roots, set CODEX_DISCORD_ATTACHMENT_ROOTS using your platform path delimiter:

export CODEX_DISCORD_ATTACHMENT_ROOTS="/path/to/repo:/path/to/exports"

On Windows PowerShell:

$env:CODEX_DISCORD_ATTACHMENT_ROOTS="C:\path\to\repo;C:\path\to\exports"

Configuration Reference

Variable

Default

Meaning

DISCORD_BOT_TOKEN

required

Discord bot token

CODEX_DISCORD_STATE_DIR

~/.codex/discord

Bridge state directory

CODEX_COMMAND

codex

Codex executable

CODEX_WORKDIR

process cwd

Working directory for Codex

CODEX_SANDBOX

read-only

Codex sandbox mode

CODEX_APPROVAL_POLICY

never

Codex approval policy for non-interactive bot mode

CODEX_MODEL

unset

Override Codex model

CODEX_PROFILE

unset

Use a Codex profile

CODEX_RESUME_BY_CHANNEL

false

Resume one Codex thread per Discord channel

CODEX_TIMEOUT_MS

900000

Codex process timeout in milliseconds

CODEX_EXTRA_ARGS

unset

Extra arguments passed to Codex

CODEX_SKIP_GIT_REPO_CHECK

true

Pass --skip-git-repo-check to codex exec

CODEX_DISCORD_ATTACHMENT_ROOTS

cwd, workdir, inbox

Allowed outbound file roots

CODEX_DISCORD_GENERATED_IMAGES_DIR

~/.codex/generated_images

Codex image_gen output dir surfaced by latest_generated_images and always allowed for attachments

CODEX_DISCORD_RELAY_ATTACHMENTS

true

bot mode: auto-attach images and outbox files produced by each run

CODEX_DISCORD_OUTBOX_DIR

~/.codex/discord_outbox

Base directory Codex is told to save relay deliverables under (one subdirectory per channel)

CODEX_DISCORD_RELAY_DOWNLOAD_ATTACHMENTS

true

bot mode: download inbound attachments into the inbox and give Codex their local paths

CODEX_DISCORD_REPLAY_MAX_AGE_MS

3600000

bot mode: replay pending messages younger than this after a restart; 0 disables replay

CODEX_DISCORD_ASSUME_YES

false

Suppress writable unattended bot warning

Troubleshooting

codex-discord-mcp doctor
codex-discord-mcp access show

If the bot receives empty message content, enable Message Content Intent in the Discord Developer Portal.

If bot mode cannot launch Codex, set CODEX_COMMAND to the full executable path or run the bridge from the same shell where codex exec "hello" works.

If MCP tools do not appear, run:

codex-discord-mcp print-config --npx

Then add the printed snippet to Codex config and restart Codex.

Development

npm install
npm run typecheck
npm test
npm run build

Development commands:

npm run dev:mcp
npm run dev:bot

Release

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

  1. Make sure npm trusted publishing is configured for Openclaw-Metis/codex-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.3.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.

The package itself ships the codex-discord-mcp bin, a files whitelist, and a prepublishOnly gate (typecheck, tests, build).

Available Tools

11 tools
bridge_statusA

Show bridge state path, queue counts, and Discord login status.

Inputs: no named parameters.

download_attachmentA

Download all attachments from a Discord message into the local bridge inbox and return absolute paths.

Inputs: chat_id (required), message_id (required).

edit_messageA

Edit a Discord message previously sent by the bot.

Inputs: text (required), chat_id (required), message_id (required).

fetch_messagesB

Fetch recent Discord channel history, oldest first. Discord's bot API does not expose full search.

Inputs: channel (required), limit.

latest_generated_imagesA

Return absolute paths of the most recently generated images from Codex's built-in image_gen output directory (default ~/.codex/generated_images), newest first. Use this to recover the path of an image you just generated so you can attach it via the files array of reply or send_message.

Inputs: limit.

list_pending_messagesA

List queued inbound Discord messages that have not been marked handled. Use this because Codex MCP has no Discord push channel.

Inputs: limit.

mark_message_handledA

Mark a queued Discord message as handled after replying or deciding no reply is needed.

Inputs: queue_id (required).

reactA

Add an emoji reaction to a Discord message. Unicode emoji work directly; custom emoji use Discord custom emoji syntax.

Inputs: emoji (required), chat_id (required), message_id (required).

recover_generated_imageA

Recover the most recently generated image(s) from the active Codex session rollout and write them to disk. Codex's built-in image_gen shows an inline preview but usually writes no file; this decodes the image from the session log and saves it to the generated-images dir, returning absolute path(s) ready to pass to the files array of reply/send_message. Optional count (default 1) and session_file (absolute rollout path; defaults to the newest session).

Inputs: count, session_file.

replyA

Reply in Discord. Pass chat_id from a queued message. Optional reply_to threads under a Discord message id. Optional files are absolute local paths.

Inputs: text (required), chat_id (required), files, reply_to.

send_messageA

Send a Discord message to an allowlisted chat. Same behavior as reply, but the name is explicit for non-reply sends.

Inputs: text (required), chat_id (required), files, reply_to.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation3/5

    reply and send_message are described as identical in behavior, causing clear overlap and potential misselection. latest_generated_images and recover_generated_image also serve similar purposes with subtle differences that could confuse. Other tools are distinct enough.

    Naming Consistency3/5

    Naming mixes verb_noun patterns (send_message, edit_message) with bare verbs (reply, react) and noun phrases (latest_generated_images, bridge_status). While most names are readable, the inconsistency undermines predictability.

    Tool Count4/5

    At 11 tools, the count is reasonable for a Discord integration, though a few tools (reply/send_message) appear redundant and could be consolidated. Not excessive or thin.

    Completeness4/5

    Core Discord operations (send, edit, react, fetch, attachments) are covered, along with a queue mechanism and status check. Missing delete message and channel listing are minor gaps; agents can work around them using existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP server that lets any MCP client start a Codex thread and continue it by opaque thread ID through the codex and codex-reply tools, with fail-closed sandboxing and approval policies. It restores the removed Codex CLI MCP integration by bridging clients like OpenCode to the official Codex SDK.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A local MCP bridge that connects existing Codex and Claude Code conversations with DSH Web, enabling delegation, result retrieval, and human-in-the-loop coordination without leaving native chat apps.
      11
      1
      MIT