COD Loadout for AI assistants and developers

Files for crawlers and scripts

These files are static, public and need no key. They are rebuilt with the site and change only when the data is refreshed, so fetch one once and keep it until its date changes. The Modern Warfare 4 files are listed here.

Which numbers come from where

Two layers are kept apart in every file, every page and every MCP result.

Activision-published

Fire rate, magazine, reserve, weapon levels, unlock levels, attachment types, Apex Attachments and what they block, perks, equipment and killstreaks. They come from Activision's launch posts and carry the data date October 24, 2026. MCP results mark them with the status "official".

Community-reported

Weapon base stats and what attachments change (CODMunity), builds and pick rates (CODMunity), tier placements (ggranked, DMZ Radar) and the standard attachment list. Community sites report them, nobody has verified them, and a patch can change them. Each file and result carries the date it was read. MCP results mark them with the status "community-reported".

What is not here

A damage table and time to kill are not published by Activision, and the site does not compute or estimate them. The only time-to-kill figures are the milliseconds one community tier list reports, shown as that list's own measure. When a source does not report a value, the file says null or "not reported". It never writes 0.

MCP server

COD Loadout runs a read-only Model Context Protocol server. The endpoint is https://codloadout-mcp.worker-rebi.workers.dev/mcp. It speaks Streamable HTTP in stateless mode: one JSON-RPC 2.0 request in a POST, one JSON response. There is no account, no key and nothing to install.

The tools read the JSON files listed above at request time and cache them for five minutes, so an answer always matches the site. Every result names the layer each number comes from, says whether it is official or community-reported, gives the data date and gives the page to cite. Names are matched without regard to case or punctuation, and a miss returns a list of near matches.

Example call

Ask for the M4 with curl. The response below is trimmed to a few fields; the full result also lists every community base stat, the tier placements, the source files and the notes.

curl -s -X POST https://codloadout-mcp.worker-rebi.workers.dev/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_weapon","arguments":{"weapon":"M4"}}}'

{
  "weapon": {
    "id": "m4",
    "name": "M4",
    "page": "https://codloadout.gitlab.io/mw4/weapons/m4/"
  },
  "official": {
    "status": "official",
    "unlockPlayerLevel": 14,
    "weaponLevels": 72,
    "fireRateRpm": 810,
    "magazine": 30,
    "reserve": 90,
    "apexAttachment": {
      "name": "M4 Hurricane",
      "blocks": [
        "Barrel",
        "Magazine"
      ]
    }
  },
  "community": {
    "status": "community-reported",
    "pickRate": {
      "percent": 5.6,
      "mode": "multiplayer",
      "source": "CODMunity",
      "retrieved": "2026-11-04"
    }
  },
  "dataDate": "2026-11-04",
  "cite": {
    "text": "COD Loadout: M4 in Modern Warfare 4",
    "url": "https://codloadout.gitlab.io/mw4/weapons/m4/"
  }
}

The result is JSON in the content field and again, parsed, in structuredContent.

Connect a client

Any MCP client that accepts a remote server by URL needs only the endpoint address. No authentication is used. Clients name their settings differently, so look in your client's documentation for where a remote or Streamable HTTP server goes. This site does not test or vouch for particular products. The JSON below is a generic form in the layout many clients use; rename the fields to match yours.

{
  "mcpServers": {
    "codloadout": {
      "url": "https://codloadout-mcp.worker-rebi.workers.dev/mcp"
    }
  }
}

Check the connection from a terminal

These two commands show that the endpoint answers. The first initialises a session, the second lists the tools.

curl -s -X POST https://codloadout-mcp.worker-rebi.workers.dev/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

curl -s -X POST https://codloadout-mcp.worker-rebi.workers.dev/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

A browser can read the plain-text description of the server at the root of the same host. Browser clients are allowed by CORS.

How to cite

Cite the page you read, with the data date shown on it. MCP results give both in the cite and dataDate fields.

Name

COD Loadout, an unofficial Call of Duty: Modern Warfare 4 fan reference. Not affiliated with Activision or Infinity Ward.

URL

https://codloadout.gitlab.io/

Data date

October 24, 2026 for Activision-published data, November 4, 2026 for the newest community data. Use the date printed on the page or in the result you used.

• Name the page address you read, not only the site.
• Give the data date of the page or result, not the date you read it.
• Community-reported data must be attributed to its source as well as to COD Loadout: weapon stats and builds to CODMunity, tier placements to ggranked or DMZ Radar, according to the layer shown on the page.
• Do not present community-reported numbers as Activision data, and do not call them current after a patch.
• Do not state damage or time to kill for a weapon on the strength of this site. It has no such data.

Example citation

COD Loadout, "M4 in Modern Warfare 4", https://codloadout.gitlab.io/mw4/weapons/m4/, Activision-published data of 2026-10-24, community-reported stats from CODMunity read 2026-11-04.

Frequently asked questions