@modly_public/mcp-server

Modly is the all-in-one Discord moderation bot — this is the official MCP server that lets any Model Context Protocol agent (Claude Desktop, Cursor, Cline, Continue, custom agents) drive a Modly-powered guild.

Run it locally over stdio. Point it at your guild with a personal access token. Your AI assistant can then triage appeals, audit members, install recipes, save embed templates, and more — without you leaving the chat.

• Bot: https://modly.net
• Issues: https://github.com/modly-public/modly-mcp/issues
• License: MIT

Install

npm install -g @modly_public/mcp-server

…or skip global install and use npx @modly_public/mcp-server directly in your MCP host config (recommended — auto-updates with each release).

Run without npm registry

The npm package isn't published yet. Until it is, run straight from GitHub — npx clones, builds (via the prepare script), and launches in one step:

# One-liner — auto-clones + builds + runs
npx github:modly-public/modly-mcp

# Or clone + run for local dev
git clone https://github.com/modly-public/modly-mcp.git
cd modly-mcp && npm install && npm run build && npm start

The same form works inside MCP host configs — see the Host configs section below for npx github:modly-public/modly-mcp snippets.

The git-URL form pulls @modly_public/sdk straight from github:modly-public/modly-sdk, so neither package needs to be on npm yet.

Environment variables

| Variable | Required | Default | Description | |---|---|---|---| | MODLY_API_KEY | yes | — | Personal access token from Account Settings → API tokens (modly_pat_...). | | MODLY_GUILD_ID | yes | — | Snowflake of the guild to operate on. | | MODLY_BASE_URL | no | https://modly.net | Override for self-hosted Modly. |

Host configs

Which args to use?

• ["-y", "@modly_public/mcp-server"] — preferred, once the package is published to npm.
• ["-y", "github:modly-public/modly-mcp"] — works today without an npm publish; pulls source from GitHub, runs the prepare build, and launches.

The two forms are interchangeable inside any of the host configs below.

Claude Desktop

Edit claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "modly": {
      "command": "npx",
      "args": ["-y", "github:modly-public/modly-mcp"],
      "env": {
        "MODLY_GUILD_ID": "1234567890",
        "MODLY_API_KEY": "modly_pat_..."
      }
    }
  }
}

Once @modly_public/mcp-server is published to npm, swap "github:modly-public/modly-mcp" for "@modly_public/mcp-server".

Restart Claude Desktop. The Modly tools appear under the hammer icon.

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "modly": {
      "command": "npx",
      "args": ["-y", "github:modly-public/modly-mcp"],
      "env": { "MODLY_GUILD_ID": "...", "MODLY_API_KEY": "modly_pat_..." }
    }
  }
}

Cline (VS Code)

cline_mcp_settings.json in the Cline extension settings:

{
  "mcpServers": {
    "modly": {
      "command": "npx",
      "args": ["-y", "github:modly-public/modly-mcp"],
      "env": { "MODLY_GUILD_ID": "...", "MODLY_API_KEY": "modly_pat_..." }
    }
  }
}

Continue / generic MCP host

Any MCP host that supports stdio transport. Pass the same command + args + env. Full per-host walkthroughs in docs/installation.md.

Tool surface

Eighteen tools, grouped by domain:

Webhooks & embeds

| Tool | What it does | |---|---| | list_webhook_targets | List every saved outbound webhook target in the guild. | | list_webhook_groups | List every saved target group in the guild. | | list_embed_templates | List every saved embed template in the guild. | | save_embed_template | Create or overwrite a named embed template. | | send_webhook | Broadcast a saved (or inline) embed to one or more targets. | | search_webhook_deliveries | Search outbound webhook delivery history for a hook. |

Moderation & cases

| Tool | What it does | |---|---| | list_moderation_cases | List recent moderation cases, optionally filtered by user. | | lookup_member_cases | Full moderation history for a specific member. | | list_member_notes | List moderator-only notes attached to a member. |

Automod & captcha

| Tool | What it does | |---|---| | list_automod_rules | List every automod rule in the guild. | | create_automod_rule | Create a new automod rule (kind, config, scope, action). | | delete_automod_rule | Delete an automod rule by ID. | | get_captcha_analytics | Captcha pass/fail counts and active challenge state. |

Safety / appeals / forms

| Tool | What it does | |---|---| | list_evader_detections / list_evader_flags | List ban-evasion detections, filterable by risk band and resolution. | | resolve_evader_flag | Resolve a detection (confirmed / false_positive / ignored). | | list_pending_appeals | List pending appeals awaiting review. | | list_form_submissions | Forms approval queue, filterable by form and status. | | decide_form_submission | Approve or reject a form submission with optional reason. |

Custom commands

| Tool | What it does | |---|---| | list_custom_commands | List every custom command in the guild. | | save_custom_command | Create or update a custom command. | | delete_custom_command | Delete a custom command by ID. |

Engagement / automation / recipes

| Tool | What it does | |---|---| | get_leveling_top | Top-N leveling leaderboard. | | enqueue_scheduled_action | Enqueue a one-shot or cron automation rule. | | install_recipe | Install a public recipe by slug, with optional overrides. |

Full schemas (every input field, type, enum) live in docs/tools.md.

Why this surface? Read tools and safe writes only. Anything that mutates webhook URLs (which contain credentials) or escalates moderation actions (ban / kick a real human) stays dashboard-only by design — agents shouldn't be able to add a partner's webhook URL or unilaterally ban a member.

Example transcripts

Three short snippets in examples/ showing realistic uses:

• Triage today's appeals queue
• Audit a member
• Roll out a recipe

Directory map

modly-mcp/
├── src/
│   ├── index.ts            # stdio entry — wires MCP host ↔ ModlyClient
│   ├── tools.ts            # 18-tool registry with handlers
│   └── locales/
│       └── en.ts           # tool description strings
├── dist/                   # compiled output (published to npm)
├── docs/
│   ├── installation.md     # per-host install walkthroughs
│   └── tools.md            # full tool reference with schemas
├── examples/               # transcript snippets
├── package.json
├── tsconfig.json
├── LICENSE
└── README.md

| Path | What's in it | |---|---| | src/ | Server source — entry point, tool registry, locales. | | docs/ | Install + tool reference. | | examples/ | Realistic usage transcripts. | | dist/ | TypeScript build output. Don't edit. |

Contributing

See CONTRIBUTING.md. Adding a tool means: pick a name, write the JSON schema in src/tools.ts, add the description string in src/locales/en.ts, and update docs/tools.md.

License

MIT — see LICENSE.

Built with ❤ for Modly.

Last updated: 2026-04-30