MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Qumge Skills 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.
19
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Find, call and pay per call: the capability layer for agents, plus skills. One key or OAuth.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http qumge-skills-mcp https://qumge.com/mcp
# 2 — ask your agent for something these tools do
# search_skills, get_skill, list_categories and 16 more
Qumge Skills costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
QUAll 2 servers
qumge2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 qumge-skills-mcp https://qumge.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
19 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.
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 Cap — 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What the user wants to do, in their own words. e.g. 'automate posting to social media', 'extract tables from PDFs'. Omit it to browse the top-ranked skills instead. |
| category | string | no | Optional. Narrow to one category. Call list_categories to see them. |
| offset | integer | no | Skip this many results — for paging through a long list. |
| limit | integer | no | How many to return. Default 5, max 10. |
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). If the reply says the skill ships more files (REFERENCE.md, scripts/…), call again with include_files: true to get them and write each next to SKILL.md.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The skill's slug, e.g. 'AgriciDaniel/claude-seo/seo-google'. Comes from search_skills. |
| include_files | boolean | no | Also return the full text of the other files in the skill's folder. Off by default — they can be hundreds of KB. Use it when installing. |
List the skill categories and how many skills are in each. Useful when the user is browsing rather than looking for something specific.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional. Filter by name or vendor, e.g. 'claude', 'gemini'. |
| limit | integer | no | How many to return. Default 20, max 60. |
Search Qumge's Caps — paid services an agent can call, billed per call from the user's Qumge balance. A Cap (short for capability) is one finished job: somebody's API or MCP server with a price list; to you it is a set of operations. Use this when the user wants something done rather than a skill to install: 'make a promo video', 'transcribe this call'. Returns the best few with pricing, measured
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What the user wants done, in their own words. Omit to browse the most-used Caps. |
| limit | integer | no | How many to return. Default 5, max 10. |
| max_price_usd | number | no | Optional ceiling: drop Caps whose per-call price is above this, in US dollars. |
Fetch one Cap's operations, prices and how to call it, by the slug returned from search_caps. Call this before using a Cap: it lists each operation (by name), its input and output schema when the developer provided one, which routes are billable, the per-call maximum, when the call settles, and the error codes the caller may see. If the request carries the user's Qumge key, it also reports that us
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| slug | string | yes | The Cap's slug, e.g. 'autowhisper'. Comes from search_caps. |
Call a Cap on the user's behalf and return its response. Use this when you cannot make the HTTP call yourself: qumge charges the user's qumge balance and forwards the call at the same price as calling it over HTTP through Qumge. Operations and prices come from get_cap. Prefer operation + input: when the operation declares an input_schema, input is validated against it before anything is char
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| slug | string | yes | The Cap's slug, from search_caps. |
| operation | string | no | Operation name from get_cap (a route's name). Use with input; takes precedence over path/method when both are given. |
| input | object | no | Arguments for the operation. Validated against its input_schema when it has one — an invalid input is refused as a tool error (isError), and nothing is charged or forwarded. |
| idempotency_key | string | no | Stable key for retries of the same operation and input. Replays the original managed order; changed input is rejected. |
| path | string | no | The route path from get_cap, e.g. '/api/videos'. A query string may be appended or passed separately in query. |
| method | string | no | HTTP method. Default GET — the routes and their methods are in get_cap. |
| query | string | no | Query string without the leading '?'. |
| body | object/string | no | Request body. An object is sent as JSON; a string is sent as-is. |
| content_type | string | no | Only needed when body is a string and the app expects a specific type. |
| accept | string | no | Optional Accept header. |
Read your managed Cap job's cached progress, complete result and receipt for free. Use the platform job_id returned by call_cap. Ordinary reads do not invoke the provider. Set refresh_result: true to explicitly request free renewal of declared result URLs after success; the optional private provider command does not generate new work or change the receipt. Existing orders remain readable after Cap
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| job_id | string | yes | Platform job_id from call_cap, starting with ac_. |
| refresh_result | boolean | no | Optional explicit free renewal of result URLs, when the original Cap declares support; default false. |
The user's Qumge balance, plus what each Cap has spent this month against its monthly limit. Call this before a paid call when the user asks whether they can afford it, and after a 402 that says the balance or a limit stopped the call — it returns the top-up link to hand to the user. Needs the user's qumge key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
Open a developer account for the user (needs their qumge key). There is no review and no waiting: it takes effect immediately, and publish_cap works right after. Give a display name and an ISO country code; the country decides tax and payout rails later. Payout details and legal name are only needed when the user actually withdraws money.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| display_name | string | yes | The name shown on their app pages. |
| country | string | yes | ISO code like "US" or "CN" (a full country name also works). |
| username | string | no | Required if the account has no username yet: 3–30 letters, digits, _ or -. It becomes the public page /u/<username>. |
| entity_type | string | no | individual (default) or company. |
| social_links | array | no | Up to 6 public URLs (X, GitHub, LinkedIn, their website). The kind is guessed from the domain. |
List the developer's own Caps with their status (draft / live / suspended) and slug. Use it before publishing to see what already exists, and after to check what went live. Needs the developer's qumge key. (Older clients may still call this tool as list_apps.)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
Prove the developer owns the domain of their MCP server or API. Going live does not need it: an unverified Cap is live and charges callers, but the developer's earnings from it stay frozen until this passes — verifying releases them. Call with the service's https url: if the domain (or a parent domain) is already verified it says so; otherwise it returns a one-line file to serve at /.well-known/qu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| url | string | yes | The service's https url, e.g. https://api.example.com/mcp |
| check | boolean | no | true = look for the line now (after the user deployed it). |
Create or update a DRAFT Cap on the developer's behalf (requires the developer's Qumge key). Prefer manifest v2: pass manifest_url for the project's public qumge.json, and slug to select a Cap when needed. The file supplies the name, connection, operations and suggested prices; do not repeat name or override file fields. Without manifest_url, give name and either connection_config, connection_id,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| name | string | no | Store name. Required only without manifest_url; manifest publication reads it from the file and ignores this duplicate field. |
| slug | string | no | Optional URL slug. Derived from the name when omitted. With manifest_url: picks which Cap in the file to publish. |
| manifest_url | string | no | Optional: publish from the project's qumge.json instead of passing everything by hand. Give https://<domain>/.well-known/qumge.json (or the service address). Its prices are suggestions: confirm them w |
| connection_config | object | no | Reusable private service connection. Repeating the same developer/name reuses credentials when endpoint and authentication agree. |
| connection_id | string | no | Existing connection_id returned by publish_cap, belonging to this developer. Use instead of connection_config. |
| base_url | string | no | Where the API lives. Must be https. For manual publication without manifest_url, connection_config, connection_id or mcp_url. Any path in it (https://host/v2) is part of what your server receives and |
| mcp_url | string | no | Optional: publish an existing remote MCP server instead of an HTTP API. Must be https. The domain does not need to be verified to go live, but earnings stay frozen until verify_domain passes for it. Q |
| mcp_tools | array | no | Prices for the MCP tools you want listed. Include execution and result schemas for managed complete-result delivery. Tools you leave out are not published and are reported back to you. |
| summary | string | no | One line describing what it does. |
| keywords | array | no | Other names for the same thing, any language, up to 20. Agents search with a request like "scrape trending TikTok videos" — the keywords are what makes that find this app. |
| metering | string | no | Legacy usage-based mode only: reported (provider reports usage) or balance_delta (Qumge reads its balance). Managed execution needs neither usage reporting nor a usage key. |
| auth_mode | string | no | Manual service authentication; named connections declare it through connection_config.auth instead. signature (default) verifies signed requests; managed wrappers use trusted context, while legacy sig |
| upstream_token | string | no | The developer's own service key. Required for a new api_key or authenticated MCP connection, and legacy balance_delta. With manifest_url, provide it when the selected connection needs api_key authenti |
| support_url | string | no | Where users ask for help. Shown on the app page. |
| refund_policy_url | string | no | Their refund policy, if they have one. |
| skill_slug | string | no | Optional. Attach an existing skill from the catalog to this app (its documentation then shows on the app page). Ignored if the slug is unknown. |
| social_links | array | no | Up to 6 public URLs for the developer (X, GitHub, LinkedIn, their website). Shown on every app page. The kind is guessed from the domain. |
| balance_path | string | no | Only for balance_delta: where we read the balance. |
| balance_json_path | string | no | Only for balance_delta: where in that response. |
Check one of the developer's own capabilities: its status (draft / review / live / suspended) and how far the publishing checklist has got. Needs the developer's Qumge key. (Older clients may still call this tool as app_status.)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| slug | string | yes | The Cap's slug. |
Run the applicable publication checks after publish_cap, before submit_cap. Managed qumge wrapper operations use authenticated isolated fixture hooks and validate the complete fixture result. Native managed API/MCP operations check HTTP OPTIONS or MCP tools/list for connection/schema evidence without invoking generation. The verification array distinguishes connection, fixture and real_delivery sc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| slug | string | yes | The Cap's slug. |
Take one of the developer's Caps live. Nothing is reviewed before launch and nobody approves it: when the applicable connection/operation checks and price book pass, with complete billed-operation docs, this publishes the Cap immediately and agents can call it — and be charged — from then on. Run test_cap first (legacy checklist keys remain signature and end_to_end; the price book is recorded when
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| slug | string | yes | The Cap's slug. |
What a developer has earned and what is payable: the amount still inside the 30-day holdback, the amount sitting in their wallet (income from Caps — the only part that can be withdrawn), and what has already been paid out, with the most recent entries. Matured purchase amounts move into the wallet automatically. Needs the developer's Qumge key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
Ask for a payout of the developer's payable balance (Cap income only — topped-up money cannot be withdrawn). Call it once without confirmed to get the estimate (amount, channel fee, withholding tax, what actually lands), show that to the user, and only then call again with confirmed: true. Needs the developer's Qumge key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qumge_key | string | no | Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| amount_usd | number | yes | How much to withdraw, in US dollars. |
| confirmed | boolean | no | Set true only after the user has seen the estimate and agreed. |
What agents searched for on Qumge and found nothing: the demand side of the store, in the searchers' own words, with how often each was searched in the last 7 and 30 days. Useful before building or publishing a Cap — it tells you what people already want. Only the search text is stored; no user and no IP.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many to return. Default 20, max 50. |
Free
$0 forever
- 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 Qumge Skills or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Qumge Skills can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.