Overseer API

Search ARK modding knowledge from your own AI tools

Members of the ARK Modding Community Discord can connect Claude, ChatGPT, Cursor, VS Code and other AI tools to Overseer's search. It's the same search as /search: years of community modding discussions, the ARK Wiki and modding tutorials. You get the raw excerpts with links and your own AI does the thinking.

  • Sign in with Discord, or use a key
  • Public channels only
  • Free for members, with staff approval

Get access

There are two ways in, and you can use both. Staff approve each member once, to keep the archive from being bulk-copied; after that, everything you connect works.

Sign in with Discord (easiest, in apps that support it, like Claude and ChatGPT). Add https://reddwarfmods.com/overseer/mcp to the app (see Connect). It opens a sign-in page: continue with Discord and you're sent back to the app. The first time, tell staff what you'll use it for.

Or get an API key (for Claude Code, Cursor, VS Code, scripts): /overseer-api-key purpose: … in the Discord server, e.g. "Claude Code while I work on my ASA mod". The key starts with ovs_ and is shown only once, so copy it right away. Overseer keeps only a fingerprint (hash) of it.

Wait for staff approval (first time only). Overseer DMs you when you're approved (if your DMs are open), or check with /overseer-api-key action: Check my key. Until then, searches say you're waiting.

100
searches per member per day, keys and apps together
10
excerpts per search, at most
90 days
per key or sign-in; then renew (no new review needed)

You need to be a member of the ARK Modding Community Discord. Each member has one key: running the command again replaces it. /overseer-api-key action: Delete my key turns off your key and disconnects every app you signed in to.

Connect your AI tool

Overseer is an MCP server with a single tool, search_ark_modding. Where a setup uses a key, replace ovs_YOUR_KEY with yours.

Claude Code

With a key:

claude mcp add --transport http overseer https://reddwarfmods.com/overseer/mcp --header "Authorization: Bearer ovs_YOUR_KEY"

Or leave out the --header part, then run /mcp in Claude Code and choose Authenticate to sign in with Discord.

Claude (desktop app or claude.ai)

Settings → Connectors → Add custom connector. Name it Overseer, use this URL, then click Connect and sign in with Discord:

https://reddwarfmods.com/overseer/mcp

Prefer a key? Use https://reddwarfmods.com/overseer/mcp?key=ovs_YOUR_KEY instead (this screen can't send headers, so the key goes in the URL).

Cursor

In ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "overseer": {
      "url": "https://reddwarfmods.com/overseer/mcp",
      "headers": { "Authorization": "Bearer ovs_YOUR_KEY" }
    }
  }
}

VS Code (GitHub Copilot)

In .vscode/mcp.json:

{
  "servers": {
    "overseer": {
      "type": "http",
      "url": "https://reddwarfmods.com/overseer/mcp",
      "headers": { "Authorization": "Bearer ovs_YOUR_KEY" }
    }
  }
}

ChatGPT and other MCP apps

Any app that accepts a remote MCP server (Streamable HTTP) works. Apps that support MCP sign-in (OAuth), such as ChatGPT's custom connectors, only need the URL https://reddwarfmods.com/overseer/mcp and sign you in with Discord. Otherwise, send your key as an Authorization: Bearer header, or use the ?key= URL above if the app can't add headers.

Cursor and VS Code can also sign in instead of using a key, in versions that support it: leave out the headers line.

Scripts and other tools (plain web API)

GET or POST https://reddwarfmods.com/overseer/api/search with q (required), game (ASA or ASE, optional) and limit (1–10, default 5):

curl -H "Authorization: Bearer ovs_YOUR_KEY" \
  "https://reddwarfmods.com/overseer/api/search?q=custom+engram+not+showing&game=ASA"

It returns JSON:

{
  "query": "custom engram not showing",
  "game": "ASA",
  "remaining_today": 99,
  "results": [
    {
      "n": 1,
      "source": "discord",          // discord | wiki | youtube
      "title": "#asa-blueprints",
      "game": "ASA",
      "date": "2025-03",
      "url": "https://discord.com/channels/…",
      "excerpt": "Person A: my engrams don't show up…\nPerson B: add them to the …"
    }
  ]
}

Errors return a non-200 status with {"error": "…"}: 401 for a missing or invalid key, 403 while you're waiting for staff approval, 429 for a limit, 503 when Overseer is offline.

Once connected

Just ask your AI about ARK modding, e.g. "My custom engram isn't showing in the engram list in ASA. What am I missing?" It decides when to search Overseer, reads the excerpts and links the Discord threads it used. If it answers from memory instead, say "search Overseer for…". Mention ASA or ASE, and use exact error text, class names and node names: they find the best matches. Each search counts toward your 100 a day, and one question can take a few.

Good to know: results come straight from Overseer, which runs on a community member's PC, so the API is unavailable if that PC is offline or restarting (rare, and usually only for a minute or two). Searches take a second or two.

Rules & privacy

What you get

  • Only public content: channels every server member can see, plus ARK Wiki pages and tutorial transcripts. Restricted channels are never searched through the API, whoever holds the key.
  • No names: people in Discord excerpts appear as Person A, Person B… within each excerpt. Messages from members who opted out of Overseer are never included.
  • Raw excerpts, not answers: community chat can be outdated or wrong. Prefer recent posts and check the links.

Using your access

  • Keep your key private. It's tied to you, so don't share it or post it in public repos. If it leaks, get a new one (the old one stops working immediately).
  • Only sign in to apps you trust. The sign-in page shows which app is asking and where you'll be sent back. If you didn't start it, close the page.
  • Modding help and free documentation. Use it for your own modding, or to write devkit documentation and guides, as long as what you publish is free and public. Write it in your own words: don't paste excerpts wholesale. Don't bulk-download or resell the results, use them to build a copy of the archive, or use them to train AI models. Credit the community when you share what you learn.
  • Staff can revoke anyone's access if it's misused, without notice.

Privacy

  • Overseer stores the same anonymous hash of your Discord ID it uses everywhere (never your ID or name), whether staff approved you and the purpose you gave, hashes of your key and of each signed-in app's tokens, the app names, when each was created and last used, and how many searches you made each day (kept for a week). Each search is also logged (when, which app, whether it worked, how many results) for the operator's usage log, kept for a year. Your search queries aren't stored.
  • Signing in with Discord asks Discord only for your basic profile (the identify permission: no email, servers or messages). Overseer uses your Discord ID once, to check you're on the server and look up your approval, then hands Discord's token straight back. Your ID never reaches this website.
  • The relay on this website only passes searches and results along. It holds each one for a few seconds and keeps a list of valid key and token hashes. For sign-in it also keeps each app's registration (its name and return addresses) and, for up to 15 minutes, sign-ins in progress. Like any website, its host keeps standard access logs (IP address and requested URL) for a short time, so prefer sending your key as a header and searches as a POST body rather than in the URL.
  • Whatever you search, and the excerpts returned, go to the AI service you connect (Anthropic, OpenAI, Cursor…) under that service's own terms. That's your choice and your responsibility.
  • /overseer-delete-my-data also deletes your key, your approval and every app sign-in. Overseer's full privacy policy covers everything else.

Questions or problems? See Contact on the main Overseer page.