A side-by-side look at the GlaziersEdge Knowledge and Imqueue 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 Imqueue 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.
Imqueue MCP tools 14
search_docsSearch the official @imqueue docs (guides, tutorial, CLI manual, articles) and every exported symbol of every @imqueue package that publishes a generated API reference, returning the most relevant pages with their URLs. Each result names the package it belongs to. Takes a plain question or an exact symbol name such as 'RedisQueue.send', 'PgPubSub.listen' or 'watcherCheckDelay'. Answers 'how do I do X in @imqueue' and confirms a signature before code is written against it. Every result carries the page URL, which get_doc reads in full. Some capabilities are covered by two mutually exclusive packages — @imqueue/pg-prisma vs @imqueue/pg-sequelize, @imqueue/opentelemetry vs @imqueue/datadog — so for a query like 'tracing' or 'database', call list_packages for the choosing rule rather than taking whichever package ranks first, and pass `package` here to search within the one you settled on.
get_docFetch the markdown of an @imqueue documentation page by its URL (as returned by search_docs). Returns plain markdown suitable for reading and quoting. Pass a URL with a #fragment — which is what search_docs returns for a section result — to get just that section plus the heading path above it; pass the URL without one to read the whole page. Only imqueue.org (framework docs) and imqueue.com (licensing, pricing, support) URLs are fetched; anything else is refused. Very large pages are truncated, which the result reports.
list_packagesThe complete, authoritative catalogue of documented @imqueue packages, each with its current version, licence, minimum Node version, a one-line summary and its exact install command. Call this BEFORE adding any @imqueue dependency: search_docs can only find a package you already suspect exists, and this is the list. Covers typed RPC over a message queue, the Redis queue engine, the `imq` CLI, jobs and scheduling, Prisma and Sequelize database toolkits, method caching, tag-invalidated caching, PostgreSQL LISTEN/NOTIFY, Zod validation, OpenTelemetry or Datadog tracing, async logging, GraphQL N+1 batching across services, CIDR/IP checks and HTTP rate limiting. Some pairs are mutually exclusive — pg-prisma vs pg-sequelize, opentelemetry vs datadog — and installing both of a pair breaks silently, so read the `pick` rule on those entries before choosing. For one package's release history, links and the framework-wide Node and Redis requirements, use package_status.
package_statusThe current version, licence, minimum Node version and last release date of any published @imqueue package — or of all of them. Use it when the user asks which version of an @imqueue package is current, what licence it is under, or which Node or Redis version it needs. Covers every published package, including @imqueue/cli and @imqueue/mcp, and also returns the framework-wide licence, Node and Redis requirements, with a `licenseNote` that states the licence terms in a sentence. The facts are read from the npm registry by imqueue.org, and the result says when. Pass `package` for one entry, with or without the @imqueue/ scope; omit it for all of them.
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. Imqueue MCP belongs to Developer Tools and uses a local stdio subprocess. Pick GlaziersEdge Knowledge for developer tools work and Imqueue 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. Imqueue 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 imqueue-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. Imqueue MCP has 64/100 (Good) with 4 views, 0 installs and 1 GitHub stars.
scaffold_serviceREAD-ONLY: returns generated source code as text and writes nothing to disk, creates no project and runs no command. Generates an idiomatic @imqueue/rpc service (an IMQService subclass with @expose()d, JSDoc-typed methods) plus a bootstrap that starts it. Provide the methods you want, or omit them for a starter template. Any non-primitive parameter or return type also gets a types.ts with the required @classType()/@property() declarations — without those the generated client types it `any`, which compiles. Use create_service (local install only) if you want files actually written.
scaffold_clientREAD-ONLY: returns text and writes nothing to disk, and does NOT run the command it shows you. Explains how to generate and use the fully-typed client for an @imqueue service: @imqueue generates the real client from a running service via `imq client generate`, so this returns that exact command plus an illustrative usage snippet. The generated file exports a single namespace holding the client class, so the import shape is not the obvious one — take it from `namespace` rather than guessing. Use generate_client (local install only) if you want the command actually run.
cli_statusDetect whether the `imq` CLI (@imqueue/cli) is installed on this machine and report its version. create_service and generate_client need it; the scaffold_service and scaffold_client tools do not.
cli_helpRun `imq [command] --help` and return the exact, version-accurate flags for a command (e.g. 'service create', 'client generate'). The flags it lists are the ones create_service accepts. Read-only: it prints help and exits.
create_serviceScaffold a real, provider-wired @imqueue service via `imq service create`. Runs as a DRY-RUN by default: it shows the plan and writes nothing. With apply=true it writes files into the target directory and may initialise git, configure CI and push to a remote. Accepts `imq` flags (cli_help lists them) to avoid interactive prompts. Requires the `imq` CLI.
generate_clientRun `imq client generate <Service>` to emit the real, fully-typed client, writing it into the output directory. The target service must be RUNNING — the CLI introspects the live service over its message queue. Requires the `imq` CLI.
cli_installInstall @imqueue/cli globally via `npm install -g @imqueue/cli`, replacing any `imq` already installed. cli_status reports whether it is already present. A global install may require a user-writable npm prefix or elevated permissions.
fleetRun `imq ctl <action>` over a directory of service repositories. `status` reports what is running and changes nothing; `start`, `stop` and `restart` change which processes are running on this machine. Requires the `imq` CLI.