Storeport

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Shopify developer docs, API learning, GraphQL introspection, and code validation.

Overview

Storeport's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Storeport in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

storeport

storeport is a small companion for building on Shopify. Shopify's developer surface is broad — many APIs, a large GraphQL schema, and a lot of documentation — so storeport gathers the everyday developer tasks into one place: start learning an API with guided context, search the documentation and pull a full page when a chunk is not enough, look up types and fields in the Admin GraphQL schema, ask the developer assistant a direct question, and check GraphQL and component code blocks before they ship. One binary serves a command-line interface and a stdio MCP server.

No Shopify store token and no API key are required. The upstream is Shopify's public developer service, and storeport sends no authorization header. The base URL defaults to https://shopify.dev and can be overridden with the SHOPIFY_DEV_BASE_URL environment variable.

Install

bash
npx @reneturcios/storeport search "metafields"

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/storeport

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash
storeport learn admin-graphqlstoreport learn functions --conversation-id conv-1storeport search "checkout extensibility"storeport search webhooks --max 5storeport docs https://shopify.dev/docs/apps/build/checkoutstoreport docs /docs/api/admin-graphqlstoreport introspect Productstoreport introspect Order --api-version 2025-10storeport ask "How do I store extra product data?"storeport validate-graphql '{ shop { name } }'storeport validate-components '<s-page heading="Hi"></s-page>'
storeport --version

Each command prints the upstream JSON payload. Exit codes: 0 on success, 1 when a call fails (including an upstream API error), 2 for usage errors. Empty queries, prompts, content, and URLs are rejected before any request is made.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/storeport mcp

MCP client configuration:

json
{  "mcpServers": {    "storeport": {      "command": "npx",      "args": ["-y", "@reneturcios/storeport", "mcp"]    }  }}

No env block is needed: the server is keyless.

Tools

ToolInputWhat it returns
learn_shopify_apiapi (required), conversationId (optional)The guided learning context for the named API.
search_docs_chunksquery (required), maxNumResults (optional)The most relevant documentation chunks.
fetch_full_docsurl (required)The full text of one documentation page; an absolute URL is fetched as-is, a path is joined to the base URL.
introspect_graphql_schemaquery (required), apiVersion (optional)Admin GraphQL types and fields matching the term.
prompt_shopify_dev_assistantprompt (required), conversationId (optional)The developer assistant's answer.
validate_graphql_codeblockscontent (required), apiVersion (optional)Validation results per GraphQL code block.
validate_component_codeblockscontent (required)Validation results for Shopify component code blocks.

All calls go to the Shopify developer service under the configured base URL (default https://shopify.dev). This build covers a core subset of the documented developer surface: Liquid/theme codeblock validation, component validation for other frameworks, and docs update/feedback tools are not included.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit 878f1a9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts