MCP server for interacting with the Scryfall MTG API
Modkeel is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Modded Minecraft: which mod crashed, where to get a mod for your version, which mods work together.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http modkeel-mcp https://api.modkeel.com/mcp
# 2 — ask your agent for something these tools do
# diagnose_crash, search_mods, get_mod_info and 4 more
Modkeel costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http modkeel-mcp https://api.modkeel.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find the mod most likely behind a modded Minecraft crash (Fabric, NeoForge, Forge). Use it whenever the user shares a crash report or latest.log or says the game will not start. It is the only tool that reads logs, and it adds what the file does not hold: it checks every installed mod against the Modkeel lab (pairs in the pack that clashed, jars that crashed on that Minecraft version), says how ma
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | The full crash report (crash-reports/crash-*.txt, from '---- Minecraft Crash Report ----') or logs/latest.log, unedited. Up to 4 MB. Give text or url. |
| url | string | no | A link to the crash report or log on a paste site (mclo.gs, pastebin.com, paste.ee, gist.github.com, modkeel.com), e.g. https://mclo.gs/abc123. Modkeel downloads the raw text itself. Give text or url. |
Turn a mod's display name or part of its id into the exact mod id the other lab tools take, and see which mods the Modkeel lab has data on. Use it first when you only have a name ("Entity Culling", "Sodium") or are unsure of the id; skip it when you already have the id. To download a mod, call find_mod_download with its name instead: it finds the mod itself. Matching ignores case, spaces and punct
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Mod name or part of its id, e.g. "Entity Culling", "sod" or "create". Empty or omitted: list every mod the lab tested. |
| mc | string | no | Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count. |
| limit | integer | no | How many mods to return, 1 to 100. Default 25. |
What one Minecraft mod is and where to get it: its Modrinth page (title, summary, categories, loaders, the Minecraft releases its author lists, client/server side, licence, downloads, source and issue links) next to a short Modkeel lab record (tested versions, run and pair counts). Use it for "what does this mod do?", "is it client-only?", "where do I download it?" or to link a suspect from diagno
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mod_id | string | yes | Lab mod id (e.g. fabric_api, ferritecore) or Modrinth slug (e.g. fabric-api, sodium-extra), lowercase. Unsure? Call search_mods first. |
The exact file to install for one mod on one Minecraft version and loader, with its download link. Use it for "where do I get X for 26.2 Fabric?", after diagnose_crash names a mod that needs another build, or when updating a pack to a new version. Checks, best first: the author's own build on Modrinth (status official: file, required mods, and lab runs of that exact file), a community port the Mod
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mod_id | string | yes | The mod's name as the user wrote it (e.g. Entity Culling), a lab mod id (e.g. sodium, fabric_api) or a Modrinth slug (e.g. fabric-api). |
| mc | string | yes | Minecraft version to install on, exactly, e.g. 1.21.1 or 26.2. |
| loader | string | yes | Mod loader of the instance: fabric, neoforge, forge or quilt. |
Everything the Modkeel lab saw one Minecraft mod do: each Minecraft version where it ran on a server or a client, or crashed, and every mod it ran with or clashed with. Use it for "does this mod work on 1.21.1?", "which versions was it tested on?" or to check a suspect from diagnose_crash. For one specific pair of mods, check_mod_pair gives a direct verdict; for what the mod is and where to get it
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mod_id | string | yes | Lowercase mod id as the loader knows it (the Modrinth/Fabric/NeoForge id, e.g. sodium, create, entityculling), not the display name. Unsure of the id? Call search_mods first. |
| mc | string | no | Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count. |
Whether two Minecraft mods ran together in the Modkeel lab, clashed, or were never tested together. Use it for "can I use X with Y?" or to check two suspects from diagnose_crash; for one mod's whole record, use get_mod_runs. Takes two mod ids in any order (from names, call search_mods first). Unknown ids are not an error: the verdict is untested, meaning no lab run, never a known conflict. With mc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mod_a | string | yes | First mod. Lowercase mod id as the loader knows it (the Modrinth/Fabric/NeoForge id, e.g. sodium, create, entityculling), not the display name. Unsure of the id? Call search_mods first. |
| mod_b | string | yes | Second mod, same format, e.g. iris. |
| mc | string | no | Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count. |
A whole mod list or modpack checked against the Modkeel lab at once: every pair in it that clashed, the mods whose jar crashed, the pairs that ran together, and the mods the lab has no data on. Use it for "will these mods work together?" or before updating a pack; for two mods, check_mod_pair is enough. Takes up to 300 mod ids (from names, search_mods first; unknown ids just land in untested_mods)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mod_ids | array | yes | Lowercase mod ids as the loader knows them, e.g. ["sodium", "iris", "create"]. The ids of a mods folder's jars work. |
| mc | string | no | Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Modkeel or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Modkeel can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.