v0.2.1

0.2.1 - 2026-11-12

Added

• A Publish to MCP Registry workflow that publishes server.json with GitHub OIDC, pins mcp-publisher and verifies its release checksum. The official registry entry for io.github.TheStreamCode/discord-management-mcp is now maintained from CI without stored credentials.

Fixed

• discord_set_channel_permissions now applies the requested allow/deny overwrite instead of silently keeping the previous bits. It replaces the overwrite with permissionOverwrites.create (discord.js edit ignored PermissionsBitField payloads), rejects a permission listed as both allowed and denied, and reads the applied overwrite back so it cannot report success when Discord did not apply the change.

v0.2.0

Release 0.2.0.

Highlights

• Seven new tools (54 total): audit log, role member counts, ban list, member search, incident actions, bulk ban, voice channel status.
• Discord channel obfuscation handled before the 2026-11-16 deadline: backups and channel listings report coverage and hidden channels instead of silently losing them.
• Real-API fixes found in live testing: channel mutations used the removed ^[ditable getter instead of manageable; threads were captured as channels; role colors used the deprecated field.
• Safety: atomic backup writes, containment re-validated on every access, FIFO mutation queue, plan hashes, NOT_RESTORED reporting, pre-restore backup IDs on every path, backup guards for permission and guild-setting changes.
• Reliability: functional LOG_LEVEL JSON logging on stderr, persistent Discord error handling, graceful shutdown with mutation drain, MCP server instructions and a protocol smoke test in CI.
• Packaging and discovery: MCP registry metadata (mcpName, server.json), publish workflow gated on audit, pack check and main ancestry, weekly dependency audit.
• Documentation: new docs/setup.md covering bot creation, permissions, invite URL, server ID, client registration, first backup and restore, usage examples and security checklist.

Verification

• 124 automated tests; lint, typecheck, build,
  pm run verify:mcp,
  pm run pack:check, runtime audit and docs lint all green.
• Live Discord test on a disposable server: 30/30 checks covering creation, updates, permission overwrites, restore plan and apply, plan-hash drift rejection and negative guards. Test server left in its initial state.

See CHANGELOG.md for the full list.

Publication

Published to npm with provenance through npm Trusted Publishing (OIDC). No long-lived npm token is used; the legacy NPM_TOKEN secret was deleted after validation.

discord-management-mcp v0.1.2

Security

• Remove invite codes and URLs from MCP responses and backup snapshots.
• Recursively sanitize legacy backup data and redact secret-bearing errors.
• Reject symbolic-link, oversized, deeply nested, or structurally invalid backup input.
• Update vulnerable transitive dependencies; runtime and complete npm audits now report zero vulnerabilities.

Reliability

• Advertise a valid root-object output schema with a consistent ok field for all 47 MCP tools.
• Stop restore apply on the first failed Discord operation while preserving the pre-restore backup ID and reporting applied, skipped, and failed work.
• Bound Discord IDs, audit reasons, arrays, payloads, and enum values; reject ambiguous bulk deletion, duplicates, and no-op updates before Discord is contacted.
• Keep complete backup payloads local: discord_backup_read now returns validated metadata, counts, and warnings.

Project presentation

• Rework the README around a package-first quick start, safety architecture, capability table, and explicit trust boundaries.
• Add optimized wide project artwork and a dedicated GitHub social-preview asset.
• Group future Dependabot security updates so independent advisories cannot deadlock one another.

Verification

• 11 test files / 38 tests passed
• Linux CI, Windows CI, CodeQL JavaScript/TypeScript, and CodeQL Actions passed
• npm run release:check -- v0.1.2, npm run preflight, and npm run pack:check passed
• runtime and complete npm audits: 0 vulnerabilities
• package dry run: 34 consumer files; no backups, secrets, source maps, or repository artwork

No live Discord mutation was performed.

discord-management-mcp v0.1.1

Fixed

• Preserve structured application errors from Discord backup tools by declaring success and failure MCP output variants.
• Add a protocol-level regression test for invalid backup IDs.
• Correct release and security documentation after the initial npm publication.

Changed

• Limit the npm tarball to consumer-facing documentation; maintainer-only planning and publishing runbooks remain in GitHub.
• Improve README installation guidance, verified badges, citation metadata, and project-specific agent instructions.

Verification

• 8 test files / 28 tests passed
• lint, type-check, build, package verification, Linux CI, Windows CI, and CodeQL passed
• runtime and complete npm audits: 0 vulnerabilities
• packed install smoke: 47 tools; mutation and traversal guards fail closed; structured errors preserved
• artifact: 30 files, 33,753 bytes; no secrets, backups, local paths, source maps, or repository-only assets detected

discord-management-mcp v0.1.0

Highlights

• Safe-by-default Discord management MCP server with guarded mutations and restore previews.
• Hardened backup validation, immutable-ID matching, role/channel positioning, and cross-guild permission mapping.
• Explicit MCP tool annotations, retry-safe Discord login, and 27 regression tests.
• Reproducible Linux and Windows CI, CodeQL, npm provenance, and a lean 32-file package.

Install

npm install -g discord-management-mcp

See the README for Discord permissions, environment configuration, and client setup.