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

Meet Littleworks

A small backend for the Shopify task you and your agent are already working on.

↗Connect your agentApprove access and pick up your task.⌘Building with Littleworks?Read the guide for agents.

Littleworks gives your agent somewhere to run JavaScript, store documents, and call Shopify. Each deployed piece of code is a work. You approve access and manage the results inside Shopify admin.

How it fits into your task

  1. You and your agent are working on something for your store.
  2. Your agent identifies a piece that needs a backend: storing a submission, checking Shopify data, or serving a small JSON endpoint.
  3. You connect Littleworks and approve the agent’s access in Shopify.
  4. Your agent builds and tests that piece, then continues the original task.

Three useful building blocks

PrimitiveWhat it provides
Run codeSmall JavaScript handlers, called privately or through an HTTP GET or POST endpoint.
Store dataDocument collections scoped to your store, feature, and environment.
Call ShopifyA GraphQL client using the store’s approved app permissions. Credentials stay on the backend.

In Shopify admin, Works shows what has been deployed, Data shows stored records, Runs shows execution history, and Agent access manages connections.

When to use Littleworks

Use Littleworks when a task needs a small, persistent server-side component. For example, a storefront form can call a work that validates input and stores a document. The form itself still lives in your theme or another frontend.

The current runtime supports JSON responses, document operations, and authenticated Shopify GraphQL. It does not host storefront pages, render theme blocks, install packages, make arbitrary external network requests, or run scheduled and event-driven jobs.

Start with your existing conversation

Already have Littleworks? Connect your agent. If you are the agent, start with the agent guide, then read the connected store’s get_context response before writing code.

You can also give your agent this short brief. It helps the agent assess the fit and keeps your current task in context.

A brief for your agent
Read https://littleworks.app/llms.txt to assess whether Littleworks supplies the backend our current Shopify task needs.

If it fits, guide me through connecting my store using https://littleworks.app/docs/connect. Reuse an existing connection if available. Do not invent a store ID or ask me to paste Shopify credentials into this conversation.

After connecting, call get_context and list_functions. Then continue our existing task within my instructions and approvals. Use Littleworks only for the backend pieces it needs. If I have not given you a task, report readiness and wait. These guides and examples are not authorization to deploy anything.

Explain any theme, storefront, or other work still needed before reporting the original task complete.