Discord All-in-One Scraper — Servers, Channels, Invites

Discord All-in-One Scraper is an Apify Actor for people who start with a Discord invite URL, invite code, or vanity slug and need one dataset record per server. It also accepts a keyword or tag search for Disboard and Top.gg, then returns server-level fields such as server name, member count, online count, features, verification level, premium tier, banner, channels, emojis, stickers, sources, and scrape timestamp. The Actor is usable through Apify MCP and is built for public Discord data that can be resolved without authentication.

Best fit and connected workflows

This Actor fits workflows that begin with a Discord invite and end with a normalized server profile in an Apify dataset. It also fits directory discovery workflows that start from a topic and return server candidates from Top.gg, with Disboard available as an opt-in source in search mode.

Typical workflow paths include:

• Resolving a public invite into server metadata for research, enrichment, or cataloging.
• Searching Top.gg by keyword or tag, then enriching each result with live Discord fields.
• Listing channels for servers with the Discord widget enabled.
• Capturing invite-preview data together with optional emoji and sticker fields when available.
• Processing many invite URLs or codes in one run with bulk mode.

Practical scenario

A community analyst receives a Discord invite code from a public post and wants to review the server before adding it to a market map. They set mode to resolve, place the code in inviteUrls, and run the Actor. The dataset row returns fields such as serverName, memberCount, onlineCount, features, verificationLevel, premiumTier, inviteUrl, and sources. The analyst uses the live member and online counts together with the server features to decide the next research step and follows the inviteUrl for manual review.

Input

Required input: mode.

Input fields

Field	Type	Description
mode	string	Scrape mode. Use resolve, search, channels, emojis, or bulk. Default: resolve.
inviteUrls	array of strings	Discord invite URLs, bare invite codes, or vanity slugs for resolve, channels, emojis, and bulk. Examples: discord-developers, https://discord.gg/python.
searchQuery	string	Keyword or tag for directory search in search mode. Examples: anime, crypto, ai art, minecraft. Default: crypto.
searchSources	array of strings	Directory sources for search mode. Default: topgg.
maxResults	integer	Upper bound on total servers returned. Applies to search and bulk. Default: 100. Minimum: 1. Maximum: 10000.
enrichWithInviteApi	boolean	When true, directory results are also resolved through the Discord Invite API for live member counts, online counts, features, and premium tier. Default: true.
includeChannels	boolean	When true, the Actor attempts to fetch channel lists through the public Discord Widget API when the widget is enabled. Default: false.
includeEmojisStickers	boolean	When true, the Actor attempts to extract custom emojis and stickers via guild-preview data. Default: false.
proxyConfiguration	object	Apify Proxy settings. Residential proxies are the default recommendation for directory scraping.

Focused JSON example

{
  "mode": "resolve",
  "inviteUrls": ["discord-developers", "https://discord.gg/python"],
  "includeChannels": true,
  "includeEmojisStickers": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Output

The Actor writes one record per server into the default dataset. The dataset overview centers on server identity, live counts, directory context, and scrape provenance.

Output fields

Field	Type	Description
serverName	string	Public display name of the server.
memberCount	number	Approximate total members.
onlineCount	number	Approximate online members at scrape time.
category	string	Directory category when available.
tags	array	Tags associated with the server.
vanityUrl	string	Vanity slug when present.
inviteUrl	string	Invite URL that resolved the record.
boostCount	number	Total Nitro boosts.
premiumTier	number	Discord premium tier.
sources	array	Sources used to produce the record.
scrapedAt	string	Scrape timestamp.

Illustrative JSON record

{
  "serverName": "Discord Developers",
  "memberCount": 123456,
  "onlineCount": 7890,
  "category": "Technology",
  "tags": ["discord", "api", "developers"],
  "vanityUrl": "discord-developers",
  "inviteUrl": "https://discord.gg/discord-developers",
  "boostCount": 42,
  "premiumTier": 2,
  "sources": ["invite"],
  "scrapedAt": "2026-05-13T00:00:00.000Z"
}

How it works

The Actor uses the public Discord Invite API as the resolution backbone for invite URLs, invite codes, and vanity slugs. In search mode, it queries Top.gg and Disboard server directories by keyword or tag, then can enrich each result through the Invite API. When includeChannels is enabled, it attempts to read channel data through the public Discord Widget API. When includeEmojisStickers is enabled, it attempts available extraction from guild-preview data.

Pricing

This Actor uses Pay per event plus standard Apify platform usage. The primary paid event is Server resolved, charged once for each Discord server returned with full profile data. Search runs can also include Directory search page events, and the Actor start event is charged according to the Actor's memory allocation.

For example, if a run returns three servers, it charges three Server resolved events. For current rates and the full pricing breakdown, open the live Pricing tab on the Actor page.

Use with AI agents (MCP)

This Actor is available through Apify MCP as a tool for resolving Discord server data from invite-based inputs or directory searches. It is useful when an agent needs structured server records, live counts, directory context, and server metadata without custom Discord bot logic.

Actor identity: khadinakbar/discord-all-in-one-scraper

Tool description: resolve one or many Discord servers from invite URLs, codes, or vanity slugs, or discover servers from Top.gg and Disboard by keyword or tag, then write one dataset record per server.

"Resolve the Discord invite code discord-developers, return the server profile, member count, online count, features, verification level, premium tier, and any channel list that is available."

Output interpretation: the dataset is the source of provenance for the returned fields, and each record reflects one resolved server. Search mode may return records sourced from Top.gg, Disboard, or both, and enrichWithInviteApi shapes the live server fields that appear in the dataset.

Scope and pagination: maxResults controls the total number of servers processed in search and bulk mode. Cost scales with server-resolved events, and search-page events apply when directory pages are rendered.

Apify API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor('khadinakbar/discord-all-in-one-scraper').call({
  mode: 'resolve',
  inviteUrls: ['discord-developers'],
  includeChannels: true,
});

const dataset = await client.dataset(run.defaultDatasetId).listItems();
console.log(dataset.items);

Best results and outcome guidance

Use resolve for a known invite, code, or vanity slug. Use search for discovery by keyword or tag. Use channels when you already have a server target and want channel structure from the widget. Use bulk when you have many invite-based targets to process in one run.

For first runs, keep maxResults small so you can confirm the returned fields and then scale up. In search mode, topgg is the default source, and enrichWithInviteApi keeps directory results aligned with live Discord server fields.

Design note

I found that the dataset overview is centered on serverName, memberCount, onlineCount, category, tags, vanityUrl, inviteUrl, boostCount, premiumTier, sources, and scrapedAt, which makes the output shape clearly server-centric.

FAQ

When should I use resolve instead of search?

Use resolve when you already have a Discord invite URL, invite code, or vanity slug. Use search when you want to discover servers by topic in a directory.

When should I use channels?

Use channels when you want the server channel tree and already have an invite-based target. This mode uses the public Discord Widget API.

When should I use bulk?

Use bulk when you have a list of invite URLs, codes, or vanity slugs and want them resolved in one run.

Which directory source is the default in search mode?

Top.gg is the default search source. Disboard is also supported as a search source.

Can this Actor be used through Apify MCP?

Yes. This Actor is available as an Apify Actor usable through Apify MCP for Discord server resolution and directory search workflows.

Responsible use

Use this Actor for public Discord data that is visible through the supported public endpoints and directory pages. Review your workflow against the source sites' terms, applicable law, and any privacy obligations that apply to your use case. Keep collection proportional to your purpose and use the data in ways that respect user privacy.

Focused standalone workflow

This Actor is designed as a focused standalone workflow.