# Discord Server Stats — Members, Voice & Features (`axery/discord-server-scraper`) Actor

Get public stats for Discord servers by ID or invite code: member counts, online presence, voice channels, features and creation date. No bot token, no login.

- **URL**: https://apify.com/axery/discord-server-scraper.md
- **Developed by:** [Axery](https://apify.com/axery) (community)
- **Categories:** Social media, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.01 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Discord Public Server Stats

Gets public statistics for Discord servers over plain HTTP — **no bot token, no OAuth, no login**.

### Scope: public server metadata only

This Actor reads two of Discord's own token-free endpoints, both of which expose only what a server owner has chosen to make public:

- **Widget** (`/guilds/{id}/widget.json`) — live online count, voice channels, and a sample of currently-online members
- **Invite lookup** (`/invites/{code}?with_counts=true`) — server name, description, approximate member and online totals

**Message content is not accessible through either, and no attempt is made to read messages, DMs, or anything behind a login.**

### What makes this different

**Server creation date, decoded — a field Discord never returns.** Discord IDs are snowflakes that encode their creation timestamp in the high bits. This Actor shifts out the worker/process/increment bits and adds Discord's epoch, giving you an exact `created_at` that no API field provides.

**A disabled widget doesn't silently vanish.** Most servers keep the public widget off — that's an owner setting, not a scraping failure. Those servers are still returned as rows with `widget_available: false` and whatever the invite lookup could supply, so a batch never looks like it succeeded on fewer servers than you asked for.

**Rate limits are honoured, not guessed.** Discord's 429 response states exactly how long to wait; the client waits that long instead of applying a generic backoff.

**The member list is labelled as a sample, not a roster.** Discord caps the widget's member array at 100 and includes only members currently online. The field is named `online_members_sample` with an explicit `online_members_sample_size`, because on any busy server it will disagree with `presence_count` — by design, not by error.

### Input

| Field | Type | Notes |
|---|---|---|
| `guildIds` | array | Numeric server IDs (15–25 digits). Gives live widget stats. |
| `inviteCodes` | array | Invite codes or full URLs — `discord.gg/xxxx` and `discord.com/invite/xxxx` both work. Gives member totals regardless of widget setting. |
| `proxyConfiguration` | object | Datacenter is enough. |

You can pass either or both. When an invite resolves to a server ID, the widget is tried too so both sets of fields get filled in.

### Known limits

- **Widget stats require the owner to have enabled it.** Roughly most servers have not.
- **Voice channels only.** The widget exposes voice channels; text channels are not included.
- **Member counts from invites are approximate** — that's Discord's own wording (`approximate_member_count`), and the field name preserves it.

### Local development

```bash
pip install -r requirements.txt
python test_local.py --out sample_output.json
python test_local.py --guilds 81384788765712384 --invites python
```

`sample_output.json` covers both cases: one server with the widget enabled, one with it disabled and read via invite instead.

# Actor input Schema

## `guildIds` (type: `array`):

Numeric Discord server (guild) IDs, 15-25 digits. Returns live widget stats: online presence count, voice channels, and a sample of currently-online members. Only works for servers whose owner has enabled the public widget - others are still returned, flagged `widget_available: false`.

## `inviteCodes` (type: `array`):

Invite codes or full invite URLs (`discord.gg/xxxx` and `discord.com/invite/xxxx` both work). Returns server name, description, and approximate member/online totals. Works regardless of the widget setting.

## `proxyConfiguration` (type: `object`):

Apify Proxy settings. Discord rate-limits by IP and tells the client exactly how long to wait; the Actor honours that instruction. Apify's automatic proxy selection is enough for normal volumes.

## Actor input object example

```json
{
  "guildIds": [
    "81384788765712384"
  ],
  "inviteCodes": [
    "discord-developers",
    "https://discord.gg/python"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `servers` (type: `string`):

One row per server: name, member/presence counts, voice channels, features, creation date.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "guildIds": [
        "81384788765712384"
    ],
    "inviteCodes": [
        "discord-developers"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("axery/discord-server-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "guildIds": ["81384788765712384"],
    "inviteCodes": ["discord-developers"],
}

# Run the Actor and wait for it to finish
run = client.actor("axery/discord-server-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "guildIds": [
    "81384788765712384"
  ],
  "inviteCodes": [
    "discord-developers"
  ]
}' |
apify call axery/discord-server-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,axery/discord-server-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HrFgnm82F17ghBOaN/builds/sEgUAzrGRoNpWQ36e/openapi.json