Tool Catalog

These are the tools the Zingasuite MCP server exposes today. Each maps to the same code path as the REST API, so behaviour and permissions match exactly. The scope column is the scope the key needs.

Discovery (resources)

An agent can read these before acting:

  • zinga://entity/profile — the entity (id, default locale/currency, enabled apps) and your key's granted scopes, so the agent knows what it may do.
  • zinga://shop/websites — your storefronts (id, slug, currency), needed to scope website-specific reads/writes.

ZingaShop

Generic resources

Five parameterised tools operate over ~30 catalog/store resources (tags, collections, brands, attributes, promotions, coupons, gift-cards, cms-pages, blog, pricelists, subscriptions, warehouses, returns, shipping, redirects, …):

Tool Scope Purpose
shop.describe_resources data:read List which resources exist and each one's writable fields
shop.query data:read List rows of a resource (paging, search, filters, website_id)
shop.get data:read Get one row by id
shop.create data:write:<resource> Create a row
shop.update data:write:<resource> Patch a row
shop.delete data:write:<resource> Delete a row (soft where supported)

Products, orders, inventory, categories

Richer purpose-built tools:

Tool Scope Purpose
shop.products.list / .get data:read Products with resolved prices, variants, media
shop.products.create / .update data:write:products Create / patch a product
shop.variants.set_prices data:write:products Set flat or quantity-break prices per pricelist/currency
shop.categories.list / .create / .update data:read / data:write:categories Manage categories
shop.inventory.get data:read Stock levels per warehouse
shop.inventory.adjust data:write:inventory Set or adjust on-hand stock
shop.orders.list / .get data:read Browse orders
shop.orders.create data:write:orders Import an order (customer + items; idempotent via externalId)

ZingaConnect (messaging)

Tool Scope Purpose
messaging.channels.list messaging:read List messaging channels
messaging.whatsapp.send messaging:send Send a WhatsApp text / template / media message
messaging.messages.get messaging:read Look up a message's delivery status
messaging.webhooks.list / .register / .delete messaging:webhooks Manage outbound webhooks

ZingaConnect (CRM)

CRM tools require a key scoped to the crm app (per-key app scope). Owner-scoped
records (deals, leads) are not exposed over the API.

Tool Scope Purpose
crm.describe_resources data:read List CRM resources + their writable fields
crm.query / crm.get data:read List / fetch contacts, accounts, lists, tags, teams, agents, pipelines, message-templates, campaigns, …
crm.create / crm.update / crm.delete data:write:<resource> Create / patch / delete a CRM record
crm.campaigns.steps.list / .add / .update / .delete data:read / data:write:campaigns Manage a campaign's drip steps
crm.campaigns.activate / crm.campaigns.pause data:write:campaigns Enrol + start, or pause, a campaign
crm.whatsapp_templates.create / .submit data:write:whatsapp-templates Draft a WhatsApp template and submit it to Meta for review

Zingalify

Zingalify tools require a key scoped to the zingalify app. (URL/tool
shorthand is zlf.)

Tool Scope Purpose
zlf.describe_resources data:read List Zingalify resources + writable fields
zlf.query / zlf.get data:read List / fetch rubrics, item-pools, item-bank, candidates, test-categories, assets, attempts, certificates, invitations, …
zlf.create / zlf.update / zlf.delete data:write:<resource> Create / patch / delete (resources produced by other flows — attempts, certificates, invitations — reject create)

Analytics

Tool Scope Purpose
analytics.shop.sales_summary data:read Order count + revenue (per currency) over a recent window; optional storefront scope

Documentation

Tool Scope Purpose
docs.search data:read Full-text search your published docs (optionally return bodies to ground an answer)

Prompts

Ready-made workflows an agent can run: create_product, restock_low_inventory, answer_from_docs.

The catalog grows over time (Zingalify and Zingasolve authoring are planned next). Agents always see the current set via the MCP tools/list call — this page is a snapshot.

Was this helpful?