Skip to main content
Glama

MeshMarket

by io.github.RightOnPar-LLC

Install Matrix

install-matrix

Install Matrix — Generate copy-paste-correct MCP install snippets for ~29 clients at once — with each client's config-key traps already encoded (Antigravity demands serverUrl and lowercase names; Gemini CLI demands httpUrl; AnythingLLM demands type 'streamable'; Goose/Kiro/Cursor/VS Code get working deeplinks; ChatGPT gets the search+fetch requirement spelled out). Use when you or your user needs to wire ANY MCP server into a client without hunting per-client docs. Deterministic, no model call. Input: {server_url: string (required, http(s) URL), name?: string, transport?: 'streamable-http'|'sse', auth?: 'none'|'bearer-optional'|'bearer-required'}. Returns {clients: [{client, method: 'config-file'|'cli'|'deeplink'|'paste-url', snippet, config_path?, notes?}], count}. (1 MESH/call, a tool · devtools)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesPayload for install-matrix

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changed
    • addedInput schema / properties / input / additionalProperties
      Added value: +true
    • addedInput schema / properties / input / properties / auth / default
      Added value: +"none"
    • changedInput schema / properties / input / properties / auth / description
      Previous value: -"whether callers need a Bearer key. bearer-* variants add an Authorization header placeholder to snippets for clients that support custom headers. Default 'none'"New value: +"none | bearer-optional | bearer-required; bearer-* adds an Authorization placeholder to snippets. Unrecognized falls back to none."
    • removedInput schema / properties / input / properties / auth / enum
      Removed value: -[
-  "none",
-  "bearer-optional",
-  "bearer-required"
-]
    • changedInput schema / properties / input / properties / name / description
      Previous value: -"server name used inside configs and deeplinks, e.g. 'meshmarket'. Default: derived from the URL host. Normalized to lowercase a-z0-9- so it satisfies the strictest client (Antigravity 400s on non-lowercase names)."New value: +"Optional server name used inside configs/deeplinks. Normalized by the handler (lowercased, non [a-z0-9_-] runs to -, truncated to 48). Default: derived from the URL host."
    • changedInput schema / properties / input / properties / server_url / description
      Previous value: -"REQUIRED — the MCP server URL to generate install snippets for, e.g. 'https://market.meshtool.ai/mcp'. Must be http(s)."New value: +"REQUIRED — the MCP server URL to generate install snippets for. Must be a valid http(s) URL; anything else returns {ok:false, error}. Aliases url and serverUrl accepted."
    • addedInput schema / properties / input / properties / server_url / format
      Added value: +"uri"
    • addedInput schema / properties / input / properties / transport / default
      Added value: +"streamable-http"
    • changedInput schema / properties / input / properties / transport / description
      Previous value: -"transport the server speaks; default 'streamable-http'"New value: +"streamable-http or sse. Unrecognized values silently fall back to streamable-http. Currently echoed only — snippets identical for both."
    • removedInput schema / properties / input / properties / transport / enum
      Removed value: -[
-  "streamable-http",
-  "sse"
-]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds meaningful behavioral context: 'Deterministic, no model call,' fallback behavior for transport/auth, error handling for invalid URLs, and the return shape. This exceeds what annotations alone provide, earning a solid 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loaded with the core purpose and concrete client examples that justify the length. Each clause adds value (trap examples, use case, deterministic behavior, input/output shapes). It could be slightly more compact, but the density is high and the structure is logical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully covers the tool's context: purpose, input structure, output structure (clients array with method and snippet), error behavior, deterministic nature, and cost. Since there is no output schema, the explicit 'Returns {clients: [...], count}' is essential and provided. This is a complete description for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides highly detailed descriptions for every parameter (normalization, fallbacks, aliases). The tool description merely summarizes the parameter list without adding new semantics. With 100% schema coverage, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb+resource: 'Generate copy-paste-correct MCP install snippets for ~29 clients at once.' It specifies the exact output (snippets, config methods) and the client-specific traps encoded. This clearly differentiates it from the sibling tools, none of which target MCP installation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states 'Use when you or your user needs to wire ANY MCP server into a client without hunting per-client docs.' This provides a concrete when-to-use scenario. It doesn't name alternatives, but given the tool's unique niche among siblings, this is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MeshMarket toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Several tools have overlapping purposes: search and mesh_discover both enumerate the catalog, while biz-analyze, task-analysis, and task-orchestrate all produce structured plans from a described situation. This will cause agents to misselect between them despite otherwise distinct tools.

Naming Consistency2/5

Naming is inconsistent: mesh_* tools use snake_case, most capability tools use hyphenated lowercase names, and a few (fetch, search) are bare verbs. There is no single verb-object or noun-verb pattern that holds across the set.

Tool Count3/5

28 tools is on the heavy side, but the marketplace concept justifies including many callable capabilities. However, the mix of platform tools and unrelated utilities makes the surface feel cluttered and hard to navigate.

Completeness4/5

The core marketplace lifecycle is well covered: signup, discover, fetch, publish, delegate, refer, follow, subscribe, and balance. Minor gaps exist (no unpublish or edit for listings), but most agent workflows can proceed without dead ends.

Resources