Koskamo

Moltline Studio MCP

A collection of 22 hosted MCP servers providing various tools for business operations, code review, data analytics, and e-commerce preparation. The specific Shopify server allows agents to validate product CSVs, check URL handles, analyze variant matrices, and verify metafield keys without requiring API keys or store connections.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Moltline Studio MCP logo, by Moltline StudioVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Moltline Studio
MCP endpoint (Streamable HTTP)
https://mcp.moltlinestudio.com/shopify
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

6 of 6 have a description · 6 of 6 declare behavior hints · 6 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to moltlinestudio.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Validate product CSV files for import
  • Check URL handles for correctness
  • Analyze variant matrices
  • Verify metafield keys

Source and maintenance

Vendor evidenceRegistry 1.2.0
Maintenance checked

Protocol and capabilities

Server
moltline-shopify 1.1.0
MCP protocol negotiated in check
2025-11-25
Tools
6 advertised
Resources
0 advertised
Resource templates
0 advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "logging": {},
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "subscribe": false,
    "listChanged": true
  },
  "extensions": {
    "io.modelcontextprotocol/ui": {}
  },
  "experimental": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Shopify catalogue preparation over MCP. Free: product_csv_check, url_handle, variant_matrix, metafield_key_check. Premium (license): bulk_price_change, payout_estimate. Works on your file, not your store: no API key, no OAuth, no store access.

Tools

6 advertised

product_csv_check — Product Csv Check
Advertised by the server during the last successful anonymous check.
Advertised read-only

Check a product CSV's header row against Shopify's current columns. FREE. Catches the failure that wastes the most time: a template copied from an out-of-date guide, using column names Shopify renamed. Typical input {"header_row": ["Handle", "Title", "Body (HTML)", "Variant Price"]} returns {"ok": false, "missing_required": [], "renamed": [{"found": "Handle", "use": "URL handle"}, ...], "unrecognised": [], "verdict": "..."}. Use before an import, on the header row alone. Not for whether the values in the rows are valid: check a handle with url_handle and a metafield key with metafield_key_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "header_row must contain at least one column name"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

product_csv_check input schema
{
  "type": "object",
  "required": [
    "header_row"
  ],
  "properties": {
    "mode": {
      "type": "string",
      "default": "new",
      "pattern": "^(new|update)$",
      "description": "\"new\" when creating products, where Shopify requires only Title;\n\"update\" when changing existing ones, where it also requires URL\nhandle. Default \"new\"."
    },
    "header_row": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The CSV's first row as a list of column names, exactly as\nwritten in the file, e.g. [\"Handle\", \"Title\", \"Variant Price\"]."
    }
  },
  "additionalProperties": false
}
product_csv_check output schema
{
  "type": "object",
  "additionalProperties": true
}
product_csv_check annotations
{
  "title": "Product Csv Check",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
url_handle — Url Handle
Advertised by the server during the last successful anonymous check.
Advertised read-only

Turn a product title into a valid, unique Shopify URL handle. FREE. Shopify handles are lowercase, may contain letters, numbers and dashes, and may not contain spaces. Typical input {"title": "Men's Merino Wool Socks (2-Pack)"} returns {"handle": "mens-merino-wool-socks-2-pack", "valid": true, "changed": true, "collisions": []}. Use when generating handles for an import, or checking one you already have. Not for validating a whole header row: that is product_csv_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "title must not be empty"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

url_handle input schema
{
  "type": "object",
  "required": [
    "title"
  ],
  "properties": {
    "title": {
      "type": "string",
      "description": "The product title or a candidate handle, e.g. \"Men's Merino\nWool Socks\"."
    },
    "existing": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "Handles already used in the store or the file, so a\ncollision can be reported and a suffixed alternative suggested.\nOptional."
    }
  },
  "additionalProperties": false
}
url_handle output schema
{
  "type": "object",
  "additionalProperties": true
}
url_handle annotations
{
  "title": "Url Handle",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
variant_matrix — Variant Matrix
Advertised by the server during the last successful anonymous check.
Advertised read-only

Count the variants a set of options produces, and flag the ceilings. FREE. Option counts multiply, so three modest lists become a number nobody intended. Typical input {"options": {"Size": ["S", "M", "L"], "Colour": ["Black", "Navy"]}} returns {"option_count": 2, "variant_count": 6, "within_limits": true, "per_option": {"Size": 3, "Colour": 2}}. Use before building an import file, to find out whether the catalogue needs splitting into several products. Not for validating the resulting CSV's columns: that is product_csv_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "options must contain at least one option"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

variant_matrix input schema
{
  "type": "object",
  "required": [
    "options"
  ],
  "properties": {
    "options": {
      "type": "object",
      "description": "Option names mapped to their values, e.g. {\"Size\": [\"S\",\n\"M\"], \"Colour\": [\"Black\"]}. Each list needs at least one value.",
      "additionalProperties": {
        "type": "array",
        "items": {
          "type": "string"
        }
      }
    },
    "list_rows": {
      "type": "boolean",
      "default": false,
      "description": "When true, also return every variant combination. Off by\ndefault because the list can be very large."
    },
    "max_options": {
      "type": "integer",
      "default": 3,
      "minimum": 1,
      "description": "Ceiling on distinct option names. Default 3."
    },
    "max_variants": {
      "type": "integer",
      "default": 2048,
      "minimum": 1,
      "description": "Ceiling to check against. Default 2048, which is the\nlimit Shopify announced on 15 October 2025, up from 100. Override\nit if your plan differs."
    }
  },
  "additionalProperties": false
}
variant_matrix output schema
{
  "type": "object",
  "additionalProperties": true
}
variant_matrix annotations
{
  "title": "Variant Matrix",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
metafield_key_check — Metafield Key Check
Advertised by the server during the last successful anonymous check.
Advertised read-only

Validate a metafield namespace and key before you define it. FREE. Shopify metafield namespaces and keys are lowercase alphanumerics and underscores; a capital letter or a dash is rejected at definition time, usually after the rest of the import has already run. Typical input {"namespace": "custom", "key": "Care-Instructions"} returns {"ok": false, "problems": ["key: dashes and capitals are not allowed"], "suggested_key": "care_instructions"}. Use when designing metafields. Not for the CSV column that carries them: that is product_csv_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

metafield_key_check input schema
{
  "type": "object",
  "required": [
    "namespace",
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "The metafield key, e.g. \"care_instructions\"."
    },
    "namespace": {
      "type": "string",
      "description": "The metafield namespace, e.g. \"custom\"."
    },
    "value_type": {
      "type": "string",
      "default": "single_line_text_field",
      "description": "The intended metafield type, echoed back for your record,\ne.g. \"single_line_text_field\". Not validated against Shopify's\ntype list, which changes."
    }
  },
  "additionalProperties": false
}
metafield_key_check output schema
{
  "type": "object",
  "additionalProperties": true
}
metafield_key_check annotations
{
  "title": "Metafield Key Check",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
bulk_price_change — Bulk Price Change
Advertised by the server during the last successful anonymous check.
Advertised read-only

Apply one pricing rule across a list of prices and show the effect. PREMIUM (license). Percentage first, then the flat amount, then rounding, stated explicitly because the order changes the answer. Typical input {"prices": [19.99, 24.5], "change_pct": 10, "charm_ending": ".99"} returns {"rows": [{"was": 19.99, "now": 21.99}, {"was": 24.5, "now": 26.99}], "total_was": 44.49, "total_now": 48.98, "uplift_pct": 10.09}. Use when repricing a catalogue before export. Not for what a price nets you after Shopify's fees: that is payout_estimate. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "prices must contain at least one price"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

bulk_price_change input schema
{
  "type": "object",
  "required": [
    "prices"
  ],
  "properties": {
    "prices": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "description": "Current prices, at least one, each greater than 0."
    },
    "round_to": {
      "type": "number",
      "default": 0.01,
      "description": "Rounding increment applied last, e.g. 0.01 or 0.05.\nDefault 0.01.",
      "exclusiveMinimum": 0
    },
    "change_pct": {
      "type": "number",
      "default": 0,
      "description": "Percentage change applied first, e.g. 10 to raise by 10%\nor -5 to cut by 5%. Default 0."
    },
    "change_flat": {
      "type": "number",
      "default": 0,
      "description": "Flat amount applied after the percentage. Default 0."
    },
    "charm_ending": {
      "type": "string",
      "default": "",
      "description": "Force every price to end in these cents, e.g. \".99\" or\n\".95\". Applied after rounding. Empty by default."
    }
  },
  "additionalProperties": false
}
bulk_price_change output schema
{
  "type": "object",
  "additionalProperties": true
}
bulk_price_change annotations
{
  "title": "Bulk Price Change",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
payout_estimate — Payout Estimate
Advertised by the server during the last successful anonymous check.
Advertised read-only

Estimate what actually lands in the bank after processing fees. PREMIUM (license). Typical input {"order_total": 84.5, "fee_pct": 2.9, "fee_fixed": 0.3, "orders": 120, "refund_rate_pct": 4} returns {"gross": 10140.0, "fees": 330.06, "refunds": 405.6, "net_payout": 9404.34, "effective_fee_pct": 3.26}. Use for cash-flow planning. Not as an authoritative fee schedule: rates depend on your plan, country and card mix, so pass your own. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

payout_estimate input schema
{
  "type": "object",
  "required": [
    "order_total"
  ],
  "properties": {
    "orders": {
      "type": "integer",
      "default": 1,
      "minimum": 1,
      "description": "How many orders to model. Default 1."
    },
    "fee_pct": {
      "type": "number",
      "default": 2.9,
      "minimum": 0,
      "description": "Percentage fee per transaction. Default 2.9 (a common\npublished rate, not a promise about your account)."
    },
    "fee_fixed": {
      "type": "number",
      "default": 0.3,
      "minimum": 0,
      "description": "Fixed fee per transaction. Default 0.30."
    },
    "order_total": {
      "type": "number",
      "description": "Value of one order including anything the processor\ntakes a percentage of. Must be greater than 0.",
      "exclusiveMinimum": 0
    },
    "refund_rate_pct": {
      "type": "number",
      "default": 0,
      "maximum": 100,
      "minimum": 0,
      "description": "Share of order value refunded, as a percentage.\nDefault 0."
    }
  },
  "additionalProperties": false
}
payout_estimate output schema
{
  "type": "object",
  "additionalProperties": true
}
payout_estimate annotations
{
  "title": "Payout Estimate",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
958 ms
95th percentile latency
958 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 958 ms · metadata changed · 6 tool(s), 0 resource(s), 0 resource template(s), 0 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http moltline-studio-mcp-moltlinestudio https://mcp.moltlinestudio.com/shopify

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add moltline-studio-mcp-moltlinestudio --url https://mcp.moltlinestudio.com/shopify

Cursor

Merge this server into .cursor/mcp.json in your project, then enable moltline-studio-mcp-moltlinestudio in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "moltline-studio-mcp-moltlinestudio": {
      "url": "https://mcp.moltlinestudio.com/shopify"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "moltline-studio-mcp-moltlinestudio": {
      "type": "streamableHttp",
      "url": "https://mcp.moltlinestudio.com/shopify",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start moltline-studio-mcp-moltlinestudio and inspect its tools.
VS Code configuration
{
  "servers": {
    "moltline-studio-mcp-moltlinestudio": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/shopify"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http moltline-studio-mcp-moltlinestudio https://mcp.moltlinestudio.com/shopify

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.moltlinestudio.com/shopify

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "moltline-studio-mcp-moltlinestudio": {
      "serverUrl": "https://mcp.moltlinestudio.com/shopify"
    }
  }
}

Let your agent find its tools

Find servers like Moltline Studio MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Moltline Studio MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing