Skip to content
discord-mcp

Migrate

Migrate to discord-mcp

Section titled “Migrate to discord-mcp”

Switch from another Discord MCP server with a guided three-command flow:

  1. discord-mcp migrate --list — see available adapters.
  2. discord-mcp migrate --from <id> --source <path> — get a tool-by-tool mapping report.
  3. discord-mcp init --client <name> — generate the client config for the new server.

The migration framework is read-only and best-effort: it walks your old server’s source tree, extracts every tool name it can find, and reports which ones map onto discord-mcp’s 192-tool surface — with explicit confidence levels and explanatory notes on every non-obvious entry.

Available adapters

Section titled “Available adapters”
PaSympa TypeScript, ~91 tools, discord_* prefix.
quadslab @quadslab.io, ~138 tools, includes MCP Resources surface.
discord-ops Multi-guild routing, dry-run mode, tool profiles, ~49 tools.
Hubdustry Reference adapter (Go MCP, non-Discord) — framework smoke test.

Authoring a new adapter

Section titled “Authoring a new adapter”

Want to add support for another Discord MCP server? See the adapter authoring guide for the MigrationSource interface, detection signal patterns, the NAME_MAP convention, and the cross-detection test pattern every adapter must pass.

Three-step migration

Section titled “Three-step migration”

  1. Discover available adapters.

    Terminal window
    discord-mcp migrate --list

    Prints every adapter’s id, description, homepage, languages, and estimated tool count — pick the one matching your old server.

  2. Run the migration report.

    Terminal window
    discord-mcp migrate --from pasympa --source ~/path/to/pasympa-clone

    Outputs a structured report with three sections:

    • mapped tools — old tool name, new discord-mcp tool name, confidence (high / medium / low), and per-entry notes for non-obvious mappings.
    • unmapped tools — old tools with no discord-mcp equivalent, listed by name so you can search your agent prompts for usages.
    • manual review — items the adapter recognised but couldn’t auto-map; each carries a reason and (when known) a suggested discord-mcp tool.

    Add --json to pipe the report into jq or stash it as a CI artifact.

  3. Generate your new client config.

    Terminal window
    discord-mcp init --client claude-desktop --token "Bot YOUR.TOKEN"

    Writes the platform-appropriate config file pointing at the freshly installed discord-mcp binary. Restart your MCP client and you’re done.

What “migration” means here

Section titled “What “migration” means here”
  • Tool name mapping — which old tool corresponds to which discord-mcp tool.
  • Confidence levels (high / medium / low) with explanatory notes on every medium- and low-confidence entry.
  • Surface-area gap analysis — what the old server exposed that discord-mcp doesn’t (yet), so you know what to drop from agent prompts.

What it does NOT do:

  • Rewrite your agent prompts. The report tells you which calls to swap; you do the substitution manually because the argument shapes often differ.
  • Round-trip: there are no discord-mcp -> other adapters. Migrations are one-way, into discord-mcp.
  • Auto-translate argument shapes. Where a medium or low mapping is shown, the per-entry note describes the manual fix-up.

See also

Section titled “See also”