GlaziersEdge Knowledge vs Salesforce Metadata M… | AllMCPs
GlaziersEdge Knowledge vs Salesforce Metadata MCP
A side-by-side look at the GlaziersEdge Knowledge and Salesforce Metadata MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GlaziersEdge Knowledge for developer tools work; choose Salesforce Metadata MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
G
Choose GlaziersEdge Knowledge when
You need dedicated capabilities in the Developer Tools domain.
Its auth model fits you: No auth required.
You want tools like list_topics, get_topic, search_glazing_knowledge.
list_topicsList the 32 topics in the commercial glass & glazing knowledge base (glass types, safety glazing codes IBC 2406, storefront/curtain wall, energy codes IECC/ASHRAE 90.1/Title 24, fire-rated, hurricane/impact, wind load ASTM E1300, butt-glazed partitions, railings, sealants, testing, specs, warranties, discontinued products, glass performance data, aluminum system cross-reference, budget pricing). Returns topic numbers, titles, one-line summaries and UNVERIFIED counts. Call this first if you are unsure which topic covers a question. Responses keep the KB's confidence tags: [V] verified, [V-mfr] manufacturer claim, [UNVERIFIED], [inference], [Expert] field experience.
get_topicRead the full text of a knowledge-base topic, or a single section of it, with tables and verification tags intact. Use after list_topics or search_glazing_knowledge when you need the complete context (e.g. a whole code table). `topic` accepts a number (30), 'T30', 'Topic 30', or a title phrase ('butt glazed'); `section` accepts a section id like '30.4', 'sources', 'key', or a heading phrase like 'summary table' or 'bid-day checklist'. Long topics are paged: follow the continue_from hint. Responses keep the KB's confidence tags: [V] verified, [V-mfr] manufacturer claim, [UNVERIFIED], [inference], [Expert] field experience.
search_glazing_knowledgeKeyword search (BM25 relevance ranking) across all 32 topics; returns the best-matching sections with cited snippets (topic + section id), relevant tables, and the verification tags present. Best for free-text questions: code requirements ('IBC 2406 hazardous locations', 'IECC 2021 zone 2 SHGC'), sizing rules ('max size 1/2 tempered butt glazed'), definitions ('LSG', 'heat soak'), estimating red flags, lead-time drivers, testing standards. Use specific technical keywords. For numeric glass makeup data use lookup_glass_performance; for product equivalents use cross_reference_glass / cross_reference_aluminum_system; for budget $ use budget_price_range. Responses keep the KB's confidence tags: [V] verified, [V-mfr] manufacturer claim, [UNVERIFIED], [inference], [Expert] field experience.
lookup_glass_performanceFilter manufacturer center-of-glass performance data for 1 in. insulating glass units: Vitro (Solarban 60/70/72/90/R67/R77/R100, Sungate 400, Solarcool, Vistacool on Clear/Starphire/Acuity/Solexia/Atlantica/Azuria/Solarblue/Pacifica/Solarbronze/Optigray/Solargray/Optiblue/Graylite II; 145 makeups), Guardian SunGuard (SNX 62/27, SNX 51/23, SNE 50/25, SN 68, SN 54, SNR 50/43/35 on UltraClear/Clear/Green/CrystalGray/Gray) and Viracon (VNG-5024, VNG-4022, VNE-53, VRE-4725, VRE-4423 by substrate). Returns VLT, exterior/interior reflectance, U (air/argon), SHGC, LSG, catalog status and tags. Filter by maker, product, substrate, or limits (e.g. max_shgc 0.25 to meet IECC CZ 2). Old names like 'Solarban 70XL' or 'Solarban 67' are mapped to current names. Values are COG, not NFRC whole-product ratings. Responses keep the KB's confidence tags: [V] verified, [V-mfr] manufacturer claim, [UNVERIFIED], [inference], [Expert] field experience.
cross_reference_glassGiven a glass coating/product (e.g. 'SNX 62/27', 'Solarban 70', 'SN 68', 'VNE-53', or an old name like 'Solarban 70XL'), return equivalents from other makers with a match rating (Close / Approximate / Not supported by the numbers). Uses (1) the KB's Guardian↔Vitro chart with tested deltas (Topic 32 §32.9), (2) computed nearest makeups across Vitro, Guardian and Viracon on the same substrate color family using the KB rating rule, and (3) Topic 29 renamed/discontinued notices. Use for 'or-equal' and substitution screening (e.g. 'SNX 62/27 Vitro equivalent'). Responses keep the KB's confidence tags: [V] verified, [V-mfr] manufacturer claim, [UNVERIFIED], [inference], [Expert] field experience.
cross_reference_aluminum_systemGiven an aluminum storefront, curtain wall, entrance door, window, interior or specialty framing series (e.g. 'Kawneer Trifab 451', '451T', '1600 Wall System 1', 'Tubelite E14000', 'YKK YES 45 TU', 'EFCO 403', 'Trifab 400'), return the equivalent series from Arcadia, OBE, Kawneer, Tubelite, EFCO/Wausau, YKK AP, CRL-U.S. Aluminum and Manko for the same family (54-row Topic 28 cross-reference), with basis (face x depth, glazing plane, thermal), Verified/Flagged status, notes, and Topic 29 discontinued-series notices. Equivalent does not mean identical: always check depth, plane, glass thickness, thermal tier, performance. Responses keep the KB's confidence tags: [V] verified, [V-mfr] manufacturer claim, [UNVERIFIED], [inference], [Expert] field experience.
budget_price_rangeReturn 2026 US installed budget SELL price ranges from an experienced commercial glazing estimator ([Expert]) for a scope item: storefront, curtain wall, windows, all-glass walls/doors, folding walls, skylights, fire-rated glass/framing, entrance doors and operators, automatic sliders, glass handrails, mirrors, films, ballistic/storm-shelter glazing, sunshades, mock-ups. Units per SF, LF, each, or LS. Budget/sanity-check use only, never for bids; ranges vary by region, scope and market. Optionally include low-reliability public cross-checks. Responses keep the KB's confidence tags: [V] verified, [V-mfr] manufacturer claim, [UNVERIFIED], [inference], [Expert] field experience.
Salesforce Metadata MCP tools 20
sf_create_custom_objectCreates a new Salesforce Custom Object using the Metadata API. The object name must end with '__c'. Use this when a user asks to create a new object, entity, or table in Salesforce.
sf_create_custom_fieldCreates a new custom field on an existing Salesforce object. The field API name must end with '__c'. Supports all field types: Text, Number, Picklist, Lookup, etc.
sf_add_picklist_valuesAdds new picklist values to an existing Picklist or MultiselectPicklist field without removing existing values. Use when a user wants to add new options to a dropdown.
sf_create_approval_processCreates or updates a Salesforce Approval Process via the Metadata API. Define who can submit, approval steps with approvers, entry criteria, and what happens on approval or rejection.
sf_create_validation_ruleCreates or updates a Salesforce Validation Rule on any object via the Metadata API. The errorConditionFormula returns TRUE when data is INVALID. Use for data quality enforcement.
sf_create_workflow_field_updateCreates a Workflow Field Update action that can be referenced by Approval Processes, Workflow Rules, or Flows. Sets a field to a literal value, formula result, or null.
sf_create_formula_fieldCreates a formula field on any Salesforce object. Supports all return types (Text, Number, Currency, Date, DateTime, Checkbox, Percent) and the full Salesforce formula language: IF/AND/OR/NOT, BLANKVALUE, TEXT, VALUE, DATE, DATEVALUE, TODAY, NOW, date functions (MONTH/YEAR/DAY), math (FLOOR/CEILING/MOD), string functions (LEN/LEFT/RIGHT/MID/TRIM/UPPER/LOWER/CONTAINS/BEGINS), record type and picklist functions (ISPICKVAL, ISNULL, ISBLANK), cross-object field references (e.g. Account.Owner.Name), and VLOOKUP. Complex multi-line formulas are fully supported.
sf_deploy_metadataDeploys a set of metadata components directly to the org using the Metadata API SOAP deploy operation. Builds a package.xml and deployment zip in memory. Supports validate-only (checkOnly:true) for pre-deployment validation without making changes. Specify runTests to execute test classes during deployment (required for production). Polls until complete or timeout.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
GlaziersEdge Knowledge
No confirmed install command for GlaziersEdge Knowledge yet — follow the setup steps linked from its listing page rather than a guessed package name.
GlaziersEdge Knowledge is categorized under Developer Tools and uses an install path we have not confirmed yet. Salesforce Metadata MCP belongs to Developer Tools and uses a local stdio subprocess. Pick GlaziersEdge Knowledge for developer tools work and Salesforce Metadata MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. GlaziersEdge Knowledge has no confirmed install command yet — follow its own setup instructions.
GlaziersEdge Knowledge is listed as free. Auth: no auth required. Salesforce Metadata MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add glaziersedge-knowledge and salesforce-metadata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GlaziersEdge Knowledge has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Salesforce Metadata MCP has 63/100 (Good) with 2 views, 0 installs and 2 GitHub stars.
sf_check_deploy_statusChecks the status of an in-progress or recently completed metadata deployment by async job ID. Returns the status (Pending, InProgress, Succeeded, Failed, Canceled), component successes, failures, and test results. Use with the deploy ID returned from sf_deploy_metadata.
sf_retrieve_metadataRetrieves metadata components from the org and returns their actual file contents. Use this to read existing configuration before making changes, to back up metadata, or to check what is really deployed rather than what you think is deployed. Waits for the async retrieve to finish and unpacks the resulting zip, returning each file's path and source. Large files are truncated. Accepts 'components' (array), or 'metadataType'+'componentName' as a single-item shortcut, or a raw 'packageXml' document — provide exactly one form.
sf_delete_metadataPermanently deletes one or more metadata components of a given type via the Metadata API's deleteMetadata call — works for CustomObject, CustomField, Flow, GenAiFunction, GenAiPlugin, GenAiPlannerBundle, Bot, ApexClass, and most other metadata types. There was previously no way to remove anything created by this MCP server (sf_deploy_metadata only supports adding/updating components, not destructiveChanges) — diagnostic or abandoned metadata had nowhere to go. Deletes each fullName independently: check the response's deleted/errors lists rather than assuming all all-or-nothing. Some types have dependency order requirements (e.g. delete a Bot's GenAiFunction/GenAiPlugin/GenAiPlannerBundle before the Bot itself, delete CustomField before its parent CustomObject) — Salesforce will reject a delete that still has dependents, naming them in the error.
sf_query_recordsExecutes a SOQL query against the org and returns matching records. Provide the full SOQL string in the query param. Use for reading data, checking existing records before creating, or verifying changes.
Supports aggregate queries — GROUP BY with COUNT(), SUM(), AVG(), MAX(), MIN(), e.g.:
'SELECT StageName, COUNT(Id), SUM(Amount) FROM Opportunity GROUP BY StageName'
Aggregate results come back as regular records with the aggregate expressions as field keys (e.g. "expr0").
Row cap: 'limit' defaults to 200 and is a ceiling, not a hint. If the SOQL carries its own LIMIT the smaller of the two applies, so a LIMIT in the query can tighten the cap but never raise it. When rows are cut off the response sets truncated: true and reports appliedLimit and limitSource, so a capped result is never mistaken for a complete one.