Skip to main content
Glama
728,823 tools. Updated 2026-10-31 15:17

"How to Discover and Install Minecraft MCP Servers" matching MCP tools:

  • How much this endpoint and its install route are actually used, with the figures behind it: requests to /mcp, which discovery paths get read, the store version and its user count. Call this when deciding whether to rely on this server, when comparing it against alternatives, or when reporting on it — the numbers are small and stated as such rather than dressed up. Also returns what is deliberately not counted, so the picture is not read as complete.
    ConnectorNo auth
  • No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.
    ConnectorNo auth
  • Verify the current connection: owner.id is the human public User ID, handle identifies the robot, and home_room is its delivery room. After login or reconnect, match owner.id and handle to the approved account and robot before sending. A mismatch means stop and reload or restart the MCP client. Includes a credential-protected latest-pings feed and token-free install URL; never send credentials to the install URL.
    ConnectorNo auth
  • Get setup info for Rudow's client SDKs (Node.js backend, Python backend) — package name, install command, a minimal config/usage snippet, and how to obtain a project ingest API key. Use this to help a user add logging to their own codebase: install the right package for their stack and write the snippet into their code yourself — this tool only returns information, it does not install anything or touch the user's files. It never creates or reveals an ingest API key; the user must generate one manually from the dashboard (see key_instructions in the result) and paste it in themselves.
    ConnectorAPI key
  • Install an app on the Android device from an APK or split bundle (XAPK/APKS — how most large modern apps ship). Provide apk_url (an https link the device downloads itself — preferred, and the only workable option for real apps) or, for tiny payloads, as apk_base64. Max 300MB. Large apps can take several minutes; if this call times out the install keeps running on the device — verify with the app-list tool instead of re-installing. Use reinstall=true to uninstall then install (for signature changes).
    Connector
    Destructive
    API key

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables coding agents to run disciplined hunts over public data, enforcing evidence ledgers, calibration controls, novelty checks against catalogues and literature, and fresh-eyes review before any claim is trusted. Human-only decisions such as waivers and expert attestations stay out of reach of the agent.
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    MCP server registry and marketplace that enables dynamic discovery, installation, and activation of tools at runtime, allowing AI agents to use new tools without restarting.
    413 npm
    7
    MIT

Matching MCP Connectors

  • Video how-to search for AI agents: 2,000+ video skills, tutorials and FFmpeg recipes. No key.

  • Search, inspect and invoke every public tool on Invokera through one MCP connection.

  • Install an app on the Android device from an APK or split bundle (XAPK/APKS — how most large modern apps ship). Provide apk_url (an https link the device downloads itself — preferred, and the only workable option for real apps) or, for tiny payloads, as apk_base64. Max 300MB. Large apps can take several minutes; if this call times out the install keeps running on the device — verify with the app-list tool instead of re-installing. Use reinstall=true to uninstall then install (for signature changes).
    Connector
    Destructive
    API key
  • Install an app on the Android device from an APK or split bundle (XAPK/APKS — how most large modern apps ship). Provide apk_url (an https link the device downloads itself — preferred, and the only workable option for real apps) or, for tiny payloads, as apk_base64. Max 300MB. Large apps can take several minutes; if this call times out the install keeps running on the device — verify with the app-list tool instead of re-installing. Use reinstall=true to uninstall then install (for signature changes).
    Connector
    Destructive
    API key
  • 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 many other players hit the same crash and which fix worked for them (when 10+ did), counts lab runs of each suspect, and ranks suspects by evidence (mixin, trace, missing class) with a confidence level (NONE when nothing points at a mod). It also returns a fix guide and, when the log names the Minecraft version and loader, the build to install for the suspect and for every installed mod the lab saw crash on that version, so no follow-up call is needed. Pass the whole file as text, unedited: trimming it loses the mod list; or, when the user gave a link to a paste (mclo.gs, pastebin.com, paste.ee, gist.github.com, modkeel.com), pass url instead and Modkeel fetches it. Text with no crash in it comes back as an error to fix and retry. Up to 4 MB; read and dropped, never stored.
    ConnectorNo auth
  • 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 punctuation; best match first, then the mods with more lab data. An empty query lists every mod the lab tested. Returns each mod's id, the Minecraft versions it was tested on and how many runs and pairs it has, plus the total number of matches. No match means the lab has no data on that mod, not that it is broken (get_mod_info still finds it on Modrinth by slug). mc keeps only mods with a run on that exact version; limit caps the list, and total says how many matched.
    ConnectorNo auth
  • 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 diagnose_crash. The versions here are what the author declares; for what the lab saw run or crash, use get_mod_runs, and for two mods together, check_mod_pair. Takes a lab mod id or a Modrinth slug; from a name, call search_mods first. The project is matched by the SHA-1 of a jar the lab ran (source: jar_hash, exact), else by slug (source: slug); a mod on neither returns found: false, not an error. Asks Modrinth live on each call (nothing cached here), so it can fail when Modrinth is down: retry later.
    ConnectorNo auth
  • 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 Modkeel lab verified in one of its modpacks (port), the author's file for an earlier version that the lab ran on this one and saw start (older_build), a port the lab built from its public source and saw start but does not host (build_from_source: the repo, branch and how to build it), the loaders the author does build for that version (other_loader), else none; when that older file crashed in the lab instead, older_build says so and next_step warns against it. next_step says what the user can do in each case. For what the mod is, use get_mod_info; for whether it ran in the lab, get_mod_runs. Takes the mod's name as the user wrote it ("YUNG's Better Mineshafts"), a lab mod id or a Modrinth slug: no search_mods call needed first. Asks Modrinth live (two to five calls, nothing cached), so it can fail when Modrinth is down: retry.
    ConnectorNo auth
  • List the platform EXTENSIONS available to your organization — the org's own plus the public marketplace — so you can suggest, inspect, or install one. Each entry carries an id, label, category, short description, and its source (organization or public); public results need no hub credential, and a note tells you when the org-owned side was unavailable. Pass query with the capability the user asked for — results are relevance-ranked against it (label, category, and the vocabulary of the blueprints each extension enables) and capped to the genuine matches, so an empty list means NO extension provides that capability. Omit query to browse the whole catalog with skip/limit paging — publicTotal reports how many marketplace rows exist. Inspect a result with list_extension_surfaces / list_extension_custom_tables; install it org-wide with install_extension ONLY when your user explicitly asked for it. Read-only. Does not write files.
    ConnectorOAuth
  • Show the current MisarDev plan, how much of each quota (builds, edits, projects) is left this period, and the link to compare plans and upgrade. Call it any time — not only after hitting a limit. Reads only: it never changes the plan or takes payment. On a local install, open=true also opens the pricing page in the user's browser.
    ConnectorNo auth
  • Search the Sigistry marketplace of Claude Code plugins by keyword and/or category. Returns matches with their install command and verification status (the registry runs an eight-check security audit; prefer "verified" plugins when recommending an install).
    ConnectorNo auth
  • FREE. Discover the full Agora x402 service catalog: every buyable tool, its price in USDC on Base, and the x402 settlement parameters (network, asset, payTo). Call this first to see what you can buy and how to pay.
    ConnectorNo auth
  • Quickstart for the oruk Speech API and this MCP server: how to get an API key, per-client MCP configuration snippets, SDK install commands, and an optional routing rule the user can add to their agent instructions. No API key required. Use this when setting oruk up for the first time or when the user asks how oruk works.
    ConnectorNo auth
  • Discover AgentMarketplace's capabilities, tools, auth methods, and scopes. Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate. No authentication required. Returns a catalog of available tools, resources, auth methods, and scopes.
    ConnectorNo auth
  • Watch one TCP or UDP port on a host and report it up only when the service behind it actually answers. This is the type for game servers, databases, mail and anything else that speaks its own protocol rather than HTTP - Minecraft, Rust, CS2, FiveM, Postgres, Redis, SMTP. The port must be given as part of the url. Set protocol to UDP for game servers; most of them do not answer on TCP at all.
    ConnectorNo auth
  • Search the Sigistry marketplace of Claude Code plugins by keyword and/or category. Returns matches with their install command and verification status (the registry runs an eight-check security audit; prefer "verified" plugins when recommending an install).
    ConnectorNo auth
  • Retrieve detailed narrative information about the eSIM Finder product and connector, beyond what the search/checkout tools surface. Use this for any question that is NOT a price/plan search: how the product works, device compatibility and how to install, the Annual Travel Pass, the country coverage of a regional bundle, plan tiers, and — importantly — help when something is not working or after the user has bought (troubleshooting, error messages, managing an installed eSIM). Reach for it on any "how do I...", "what is...", "my eSIM is not working", or "what do I do after buying" question. Pass one of the following `topic` values: `about` (what the eSIM Finder connector is and its scope, plus that eSIM Finder is also a free iOS/Android app with a website FAQ and blog), `faq` (18 common Q&A pairs from esimfinder.io/faq — quick reference for first-time users), `travel-pass` (full Annual Travel Pass guide including the complete 130-destination coverage list — best when the user is weighing whether Travel Pass fits their travel pattern), `compatibility` (which phones support eSIM and how to check, per-device install steps for iPhone / Samsung / Pixel / other Android, the pre-travel checklist, and full troubleshooting — no signal or no data after install, activation and QR-code errors, specific iOS/Android error messages such as "This Code is No Longer Valid" or "Cellular Plans From This Carrier Cannot Be Added", slow data, carrier-lock, and network reset; use this whenever the user cannot get the eSIM to install or connect), `regions` (live country lists for every regional eSIM bundle currently on sale — Global, Europe, Europe Lite, Balkans, CIS, Asia, Oceania, Middle East, MENA, Africa, CENAM, Latin America, Caribbean, North America — generated from the current catalog; use this when the user asks "what countries are in X bundle?" or "how does Europe differ from Europe Lite?"), `product-overview` (what eSIM Finder is, app download links for iOS/Android, key features, support contacts, and managing an installed eSIM: safely removing or transferring it, a lost or stolen phone, finding the ICCID, hotspot/tethering, Wi-Fi calling on the primary number, and what to do when data runs low), or `plan-tiers` (compare Fixed vs Unlimited Essential vs Premium Unlimited data tiers). The response is markdown text from the eSIM Finder knowledge base; the regions topic is generated live from the current catalog. Prefer this tool over guessing — the knowledge base is the canonical source.
    ConnectorOAuth