Skip to main content
Glama

4PDA MCP

MCP server exposing the 4PDA forum lofi (text) version without a browser. Uses impit to pass Cloudflare's TLS challenge.

Why lofi?

The lofi/text version is ~50x smaller than the full page and has stable, simple markup — ideal for LLM consumption. The full version (?act=idx, ?showforum=, ?showtopic=) is JS-heavy and Cloudflare-gated.

Related MCP server: Reddit MCP Server

URL conventions (discovered)

4PDA changed the lofi entry. lofiversion/index.php?index.html now 404s. The live format is:

  • lofiversion/index.php?f{forum_id}.html — a forum page (subforums + topics list)

  • lofiversion/index.php?t{topic_id}.html — topic page 1

  • lofiversion/index.php?t{topic_id}-{offset}.html — topic page N, step 20

  • index.php?act=idx — full index, used only to enumerate top categories

The pinned header post repeats on every topic page; this server drops it on page ≥ 2.

Tools

  • list_forums(forum_id?) — top categories when forum_id omitted, else the subforums (and topics summary) of a forum as a flat list. Returns a tree the client can nest.

  • list_topics(forum_id) — topics in a forum: id, title, replies, is_important.

  • list_posts(topic_id, page=1) — posts on a page: author, date, html (with internal links rewritten to lofi where possible). Header post dropped on page ≥ 2.

Run

pip install -e .
4pda-mcp            # stdio MCP server (default)
4pda-mcp --http     # streamable HTTP server at 127.0.0.1:8000/mcp

HTTP mode options: --host (default 127.0.0.1), --port (default 8000). The HTTP endpoint serves stateless JSON-mode MCP at /mcp (GET is not supported — the server sends no notifications; DELETE/PUT return 405).

No browser, no auth needed (read-only public content). impit impersonates Chrome to clear Cloudflare.

Environment variables

Variable

Default

Meaning

FOURPDA_MIN_INTERVAL

2.0

Minimum seconds between upstream 4PDA requests (proactive throttle).

FOURPDA_API_KEY

unset

When set, HTTP requests must carry Authorization: Bearer <key>.

FOURPDA_API_KEY applies only to --http mode (stdio has no headers and is trusted). Without it the HTTP endpoint accepts unauthenticated requests. Wrong or missing token → 401 with WWW-Authenticate: Bearer realm="4pda-mcp".

Client config example (streamable HTTP + bearer):

{
  "mcpServers": {
    "4pda": {
      "type": "http",
      "url": "http://localhost:8000/mcp",
      "headers": { "Authorization": "Bearer <your-key>" }
    }
  }
}

Docker

# build locally
docker build -t 4pda-mcp .

# run without auth on port 8000
docker run -p 8000:8000 4pda-mcp

# run with a bearer key
docker run -p 8000:8000 -e FOURPDA_API_KEY=your-secret 4pda-mcp

Prebuilt multi-arch images (linux/amd64, linux/arm64) are published to GHCR: ghcr.io/mishannn/4pda-mcp — tagged latest/1/1.2/1.2.3 on releases and main on every push to main.

Rate limiting

4PDA fronts the lofi endpoint with Cloudflare; it is uncached, so every request hits origin and Cloudflare rate-limits it. The limit is not published; measured empirically (Aug 2026):

Request rate

Result

1 req / 2s

clean (10/10)

1 req / s

clean (20/20)

2 req / s (0.5s gap)

clean (30/30)

5 req / s (0.2s gap)

429 on ~20th request, Retry-After: 3600 (1h block)

The server stays well below the trip point by enforcing a minimum interval between requests (FOURPDA_MIN_INTERVAL, default 1.0 — i.e. 1 req/s, a 2x margin under the confirmed-safe 2 req/s). If a 429 still occurs, the server records the Retry-After cooldown and, without sending further requests, returns a structured rate_limited payload from every tool call:

{"rate_limited": true, "retry_after_seconds": 3600,
 "retry_at_utc": "2026-08-24T23:00:00Z",
 "hint": "4PDA is rate-limiting requests. Retry after 3600s."}

This is returned as a normal (non-error) result, so the agent can read retry_after_seconds and wait rather than hammering a blocked endpoint. The cooldown is capped at one hour so an anomalous Retry-After can't freeze the process.

Available Tools

3 tools
list_forumsA

List 4PDA forum categories/subforums. With no forum_id, returns the top-level categories (the forum tree roots). With a forum_id, returns that forum's subforums and a summary of its topics. IDs are 4PDA forum IDs.

On rate limit, returns a 'rate_limited' payload with retry_after_seconds and retry_at_utc instead of an error — wait that long before calling again.

Inputs: forum_id.

list_postsA

List posts on a page of a 4PDA topic (lofi version), with author, date and HTML body. Internal links to the full version are rewritten to their lofi equivalent where one exists. The pinned header post repeats on every page on the site; it is dropped on page >= 2. Pages are 1-indexed; each page has 20 posts.

On rate limit, returns a 'rate_limited' payload with retry_after_seconds and retry_at_utc instead of an error — wait that long before calling again.

Inputs: topic_id (required), page.

list_topicsA

List topics in a 4PDA forum (lofi version): id, title, reply count, is_important (pinned/important topics are prefixed with (!) on the site).

On rate limit, returns a 'rate_limited' payload with retry_after_seconds and retry_at_utc instead of an error — wait that long before calling again.

Inputs: forum_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool maps clearly to a different level of the forum hierarchy: forums, topics, and posts. There is minor overlap between list_forums with a forum_id and list_topics, since the former includes a topic summary, but the descriptions make the intended roles distinguishable.

    Naming Consistency5/5

    All three tools follow the exact same list_<resource> pattern: list_forums, list_topics, list_posts. This is completely predictable and makes the toolset easy to navigate.

    Tool Count5/5

    Three tools is an appropriate, lean size for a read-only forum browsing server. Each tool corresponds to a necessary step in the navigation flow: pick a forum, pick a topic, read posts.

    Completeness4/5

    The core forum traversal path is complete: forums lead to topics, and topics lead to posts. The main gap is the lack of a search tool or topic detail view, but these are reasonable omissions for a minimal browsing-focused server.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Reddit MCP Server — No API Keys Required. Browse, post, comment, vote, and manage your Reddit account from any MCP client.
      20
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to Reddit through 8 tools for searching, browsing, and retrieving posts, comments, and user data, compatible with any MCP client.
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Provides MCP-compatible AI clients with full access to a Flarum forum's API, enabling reading, searching, creating discussions, replying, moderation, and management of users, tags, and groups.
      15
      1
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      MCP server that searches and reads https://glp1forum.com (a XenForo forum) via system curl, providing tools for full-text search, thread reading, image downloads, and forum browsing without any API keys.
      5
      1
      -