Cavalera Forge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORGE_DATA_DIR | No | Folder with craft.db and market.db; when unset, the published copy is downloaded. | |
| FORGE_DATA_URL | No | Where to download the published databases from. | https://forge.cavalera.news/data |
| FORGE_CACHE_DIR | No | Directory for downloads and the UEX catalog cache. | ~/.cache/cavalera-forge |
| FORGE_MCP_OAUTH_SHIM | No | Enables the auto-approving OAuth facade for claude.ai custom connectors. | |
| FORGE_MCP_PUBLIC_URL | No | Public URL used by the auto-approving OAuth facade. | |
| UEX_MAX_CALLS_PER_MIN | No | Outgoing UEX API call budget per minute. | 40 |
| FORGE_MCP_ALLOWED_HOSTS | No | Public host names accepted (DNS rebinding protection). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| data_statusB | Game version the data is built for, data freshness, counts. |
| search_productsA | Find craftable products by name (typo tolerant). |
| product_recipeA | Crafting recipe(s) of a product: per slot the ingredient, quantity, minimum quality, and how the ingredient quality moves each stat of the product (percent at lowest and highest quality). Also the craft time and how many missions reward the product. |
| product_missionsA | Missions that can reward this product (blueprint or item), best paid first: type, faction, systems, reward, required standing. |
| ingredient_usesA | Products that use an ingredient, with quantities and a breakdown by product type. |
| craftable_fromA | Products craftable from the given ingredients: complete recipes first, then the ones closest to complete (slots covered / total). |
| mineral_infoB | Everything about a mineral: best mining locations, scan signature per rock and method, extraction profile (resistance, instability, optimal window, explosion), quality bands, best and worst refineries, best terminal sell prices. |
| mining_locationsA | Where a mineral is found, most frequent first: place, system, place type, method (ship, ROC, FPS), share of deposits and concentration range. Without a name match, lists the minerals. |
| list_mineralsB | All minerals with their number of locations, systems, and whether they are crafting ingredients. |
| identify_signatureB | What a scanner signature can be: exact multiples of a mineral's ship signature (within its cluster size), ROC/FPS deposits or salvage panels, with the number of rocks or items. |
| refinery_yieldsA | Yield bonus or malus of every refinery for a material, best first. |
| terminal_pricesC | Best trade terminals buying a mineral (refined and raw forms), price per SCU, from UEX, with the update time. |
| marketplace_searchA | UEX player marketplace listings with combined filters, ranked by quality, recency or price, one per seller, each with a direct link. Qualities read from titles are marked '~', defaults '500?'. |
| marketplace_find_itemsA | Look up items in the UEX catalog (all items, not only crafting) to get exact names and ids for marketplace_search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools target distinct resources, but mineral_info ("Everything about a mineral") is a superset that explicitly overlaps with mining_locations, refinery_yields, and terminal_prices, leaving an agent unsure whether to use the aggregate or the slice. Similarly, search_products (craftable products) and marketplace_find_items (all catalog items) have nearby boundaries that require reading descriptions to separate.
All names use snake_case and mostly follow a resource-first pattern (product_recipe, mineral_info, terminal_prices), which is predictable. Minor deviation: a few use verb ordering or bare verbs (marketplace_search, craftable_from, list_minerals), but overall readable and consistent.
14 tools is well-scoped for a mining/crafting/marketplace data server, with each tool covering a distinct query concern (recipes, missions, locations, signatures, prices). No obvious filler or redundancy in count.
The surface covers the core lifecycle well: catalog lookup, product/recipe discovery, ingredient reverse-lookup, mission rewards, mining locations, signatures, refinery yields, and terminal prices. Minor gaps exist (e.g., no explicit ship/vehicle reference or price-history tooling), but core workflows are workable.