Skip to content
littleworks

Explore the documentation

Meet LittleworksA little backend for what you’re building on Shopify.Littleworks or your own appWhat it takes to give a Shopify feature a backend: with Littleworks, or with a custom app you build and run yourself.Connect to LittleworksChoose the CLI, a plugin, or a remote MCP connection.CLIConnect from your terminal with Shopify approval and no manual tokens.Claude pluginThe Littleworks MCP connection and agent guidance in one package.OpenAI pluginThe Littleworks MCP connection and agent guidance in one package.MCP with OAuthConnect a compatible client directly, without a marketplace plugin.Build with an agentThe operating guide for agents building on Shopify with Littleworks.Write a workA JavaScript handler, a small manifest, and a version you test and then publish.Keep secretsEncrypted credentials, shared across your store’s works.Call external servicesMake public HTTPS API requests from a work using http.fetch().Store dataDocument collections with a small API, scoped automatically to the work that uses them.Call ShopifyCall Shopify’s Admin and Storefront GraphQL APIs with credentials held by Littleworks.Store filesKeep uploads such as artwork and photos in the merchant’s Shopify Files, uploaded by the browser straight to Shopify.Expose an endpointConnect an existing frontend to a work through a small JSON API.Customer access and invitationsRequire a signed-in shopper or a narrow, expiring invitation before a work runs.RecipesUseful things to build for your store, with the backend already taken care of.Product reviewsCollect customer reviews, verify purchases, and publish approved content directly into your Shopify theme.Customer wishlistsGive signed-in customers a persistent list of products they can revisit across devices.Customer quote requestsCollect a customer’s products, quantities, and requirements without turning a request into an order.Back-in-stock alertsCollect confirmed signups on sold-out variants, email them through your own provider when stock returns, and see every signup and send in your admin.Transactional emailSend email from your works through your own provider, never twice for the same thing, and see what was sent and what failed.Build a merchant pageDescribe your records and what merchants do with them; Littleworks renders a native Shopify admin page.Run works on their ownRun a work when something happens in the store, on a schedule, or from a Shopify Flow workflow.Run background jobsQueue runs for later or in the background: fan out to thousands of customers, import in pages, follow up days later, and retry what fails.MCP tool referenceTools to inspect, deploy, run, and organize the backend for a connected store.Usage and allowancesSee what your works use, how much capacity remains, and when allowances reset.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
Backend infrastructure for Shopify agents

Your agent has a plan.
Give it a backend.

Give your agent the backend it needs to build on Shopify. Run custom code, store data, and make authenticated Shopify requests—all through your agent.

Explore the docs Building with an agent?

Connect your store’s agent.

Your agentLet signed-in customers save products to a wishlist.
Draft saved
A small piece of infrastructure
littleworksYour backend
wishlist.save.js
export default async ({ input, context, db, shopify }) => {
  const { data } = await shopify.admin.graphql(
    `query ($id: ID!) { productVariant(id: $id) { id } }`,
    { id: input.variantId },
  );
  if (!data?.productVariant) throw new Error("Unknown variant");

  return db.collection("items").create({
    customerId: context.customer.id,
    variantId: data.productVariant.id,
  });
};
You stay in control, inside Shopify admin.
A small, useful foundation

Three pieces.
Plenty to work with.

Use just the pieces you need for what you’re building. Your agent writes the code; Littleworks takes care of running it.

notes.save.js
export default async ({ input, db }) => {
  const notes = db.collection("notes");

  const note = await notes.create({
    message: input.message,
    status: "new",
  });

  return { id: note.id };
};

Persistent documents. Collections created on first write.

Read the guide
Fits into the conversation

A short detour.
Then keep building.

Start where you already are: building something for your store with your agent.

  1. 01

    Your agent needs a backend

    As you build, your agent identifies where it needs code to run, data to be stored, or access to Shopify.

  2. 02

    You approve the connection

    Connect Littleworks and review the agent’s access inside Shopify admin.

  3. 03

    The work keeps running

    Your agent tests it as a draft, and you publish it when it’s ready. You can inspect runs, review data, or pause a work.

See how connecting works
Instead of building an app

Write the feature.
Skip the app around it.

A store feature is a few hundred lines. The Shopify app around it is the bigger job, and it needs looking after for as long as the feature runs. Littleworks is that app, already running.

01

No app to build

OAuth, session tokens, hosting, a database, privacy webhooks and upgrades are already handled.

02

Webhooks without the plumbing

Subscribe to a Shopify event with a filter. Littleworks verifies, de-duplicates and retries every delivery.

03

Admin pages without a UI build

Describe your records and actions; Littleworks renders a native Shopify admin page.

04

Your data, your code

Plain JavaScript and JSON you can read and export at any time.

Compare with building your own

Recipes

Your idea.
Your store’s way.

Build the behavior your store needs. Start with a recipe, adapt it with your agent, and let Littleworks supply the backend.

01

Product reviews

Collect verified reviews, approve them, and display them in your theme.

02

Customer wishlists

Let signed-in customers save products and return to them on another device.

03

Customer quote requests

Collect quantities and requirements, then give customers a place to check progress.

04

Back-in-stock alerts

Let shoppers sign up on sold-out variants and email them through your provider when stock returns.

05

Transactional email

Send email through your provider without duplicates, and see what was sent and what failed.

Explore the recipes

Made to be understood

For you.
And your agent.

Clear guides for the setup. Precise references for the code. Plain-text documentation for your agent.

01

Understand Littleworks

Where it fits, what it provides, and when to use it.

02

Connect your agent

From your existing conversation to an approved connection.

03

Read the programming guide

Handlers, manifests, storage, and the MCP interface.

llms.txt

The whole picture, ready for your agent.

Read the docs index