Skip to content
littleworksdocs

Explore the documentation

Meet LittleworksA small backend for the Shopify task you and your agent are already working on.Connect your agentApprove access once, then return to the conversation where your task started.Build with an agentThe operating guide for an agent using Littleworks as part of an existing Shopify task.Write a workA JavaScript handler, a small manifest, and an immutable version each time you deploy.Store dataDocument collections with a small API, scoped automatically to the work that uses them.Call ShopifyUse Shopify’s GraphQL API directly, with credentials held by Littleworks.Expose an endpointConnect an existing frontend to a work through a small JSON API.MCP tool referenceTen tools to inspect, deploy, run, and manage the backend for a connected store.Inspect and troubleshootFind the relevant run, understand the failure, and make the next change deliberately.Limits and securityThe current runtime boundaries, data isolation model, and execution allowances.
Shopify admin
Browse documentation
Start here
Markdown

Build with an agent

The operating guide for an agent using Littleworks as part of an existing Shopify task.

Assess the fit before connecting

Littleworks provides sandboxed JavaScript, scoped document storage, and a Shopify GraphQL client. Use it for the backend part of the merchant’s existing task. Confirm the runtime limits fit before introducing it.

Theme editing, customer-facing pages, email delivery, external API calls, scheduled jobs, and Shopify event subscriptions are outside the current runtime. Identify any required tooling for those pieces explicitly.

Connect to the right store

Use the merchant’s existing connection or ask them to follow Connect your agent. The endpoint is https://littleworks.app/mcp/STORE_ID, using the actual ID supplied by the app. Do not invent an ID, request Shopify access tokens, or replace other MCP configurations.

The server uses Streamable HTTP MCP and OAuth authorization code flow with S256 PKCE. It advertises authorization metadata and supports dynamic client registration. The merchant approves inside Shopify. One grant covers Preview and Live.

Inspect before changing anything

  1. Call get_context for the current store, granted Shopify scopes, programming interface, and limits.
  2. Call list_functions to inspect existing works, environments, active versions, and pause state.
  3. Call get_function before changing an existing work. Preserve its feature and read its source.
  4. Confirm the part of the current task that needs Littleworks. Connection approval alone is not a request to build something.

Build, test, and continue

  1. Write self-contained JavaScript and an explicit manifest. See Write a work.
  2. Deploy to Preview and invoke with suitable test data. Preview records are separate; Shopify requests still reach the real store.
  3. Inspect failures with get_run. Check for partial effects before retrying a mutation.
  4. Deploy the tested source to Live only within the merchant’s instructions and approvals. Use production in API parameters.
  5. Verify the required integration, including any frontend work outside Littleworks, before reporting the merchant’s task complete.

Read these docs as Markdown

Every guide has a Markdown link. llms.txt provides the documentation index; llms-full.txt contains all guides in one response. Both are public and contain no store data. The connected store’s get_context is the source for its current capabilities.

See the MCP tool reference for exact tool arguments.