GlaziersEdge Knowledge vs Mastercard Developers… | AllMCPs
GlaziersEdge Knowledge vs Mastercard Developers MCP
A side-by-side look at the GlaziersEdge Knowledge and Mastercard Developers 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 Mastercard Developers 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.
Mastercard Developers MCP tools 9
get-services-listLists all available Mastercard Developers Products and Services with their basic information
including title, description, and service id.
IMPORTANT: The response contains both 'Products' (business offerings) and 'Services' (technical APIs with serviceIds). Use "serviceId" for each service for any tools that require serviceId as the parameter.
get-documentationProvides an overview of all available documentation for a specific Mastercard service
including section titles, descriptions, and navigation links.
It takes one argument:
- serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')
get-documentation-section-content
Retrieves the complete content for a specific documentation section.
IMPORTANT: A section is not a single page, but rather a collection of pages that are grouped together.
It takes two arguments:
- serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')
- sectionId (str): The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')
get-documentation-pageRetrieves the complete content of a specific documentation page.
Takes one argument:
- pagePath (str): The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')
get-oauth10a-integration-guideRetrieves the comprehensive OAuth 1.0a integration guide including step-by-step instructions,
code examples, and best practices for Mastercard APIs. Optionally specify a programming language
to get language-specific examples and guidance.
get-oauth20-integration-guideRetrieves the comprehensive OAuth 2.0 integration guide including step-by-step instructions,
code examples, and best practices for Mastercard APIs. Optionally specify a programming language
to get language-specific examples and guidance.
get-openfinance-integration-guideRetrieves the comprehensive Open Finance (previously known as Open Banking) integration
guide including setup instructions, API usage examples, and implementation best practices.
get-api-operation-list
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. Mastercard Developers MCP belongs to Developer Tools and uses a local stdio subprocess. Pick GlaziersEdge Knowledge for developer tools work and Mastercard Developers 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. Mastercard Developers MCP is listed as free. Auth: no auth required. 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 mastercard-developers-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. Mastercard Developers MCP has 67/100 (Great) with 2 views, 0 installs and 55 GitHub stars.
Provides a summary of all API operations for a specific Mastercard API
specification including HTTP methods, request paths, titles, and descriptions.
It takes one argument:
- apiSpecificationPath (str): The path to the API specification file e.g., '/open-finance-us/swagger/openbanking-us.yaml')
get-api-operation-detailsProvides detailed information about a specific API operation including parameter definitions,
request and response schemas, and technical specifications for successful API calls.
It takes three arguments:
- apiSpecificationPath (str): The path to the API specification file (e.g. The path would be /open-finance-us/swagger/openbanking-us.yaml for
https://static.developer.mastercard.com/content/open-finance-us/swagger/openbanking-us.yaml,
https://developer.mastercard.com/open-finance-us/swagger/openbanking-us.yaml,
or /open-finance-us/swagger/openbanking-us.yaml)
- method (str): The HTTP method of the operation (e.g., GET, POST, PUT, DELETE)
- path (str): The API endpoint path from the specification (e.g., /payments, /accounts/{id})