mcp server
Qumge Skills
Search and install curated agent skills, plus bundles that get one job done in a single call.
Description as published by the maintainer. Source
- version 1.0.0
- active
- retrieval
active — Registry entry last updated 2026-08-05. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_bundle(slug)- Fetch every SKILL.md in one bundle, in a single call. Write each returned skill to .claude/skills/<name>/SKILL.md (or the equivalent for the user's agent) and the whole set is installed — no other step is needed. Get the slug from list_bundles. Required: slug.
get_skill(slug)- Fetch the full SKILL.md content of one skill, by the slug returned from search_skills. Write the returned markdown to .claude/skills/<name>/SKILL.md (or the equivalent for the user's agent) and it is installed — no other step is needed. Required: slug.
list_bundles- List Qumge's skill bundles. A bundle is a hand-picked set of skills that together get ONE job done — e.g. 'see what competitors are posting'. Use this when the user describes a goal rather than naming a tool, then call get_bundle to install the whole set in a single step.
list_categories- List the skill categories and how many skills are in each. Useful when the user is browsing rather than looking for something specific.
list_models(limit, query)- List the models this gateway can route to, best first. Every one is reachable with the same Qumge key — no per-vendor signup. Only tool-calling models are listed: an agent cannot use the others.
search_skills(limit, query, offset, category)- Search Qumge's curated catalog of agent skills (SKILL.md files) by what the user wants to accomplish. Use this whenever the user asks for a skill, tool, or capability — e.g. 'find me a skill for social media automation', 'is there a skill for SEO audits'. Returns the best few, ranked by how useful they actually are (an LLM read each one), with a one-line summary and the exact slug to pass to get_skill.
Last successful function declaration observed on . Source: https://qumge.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://qumge.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-05 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-05 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | qumge.com | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | qumge.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json