LabscoMCP early access ↗
contentstack avatar

contentstack-vibe-docs

AI impact score: 3 out of 5 for usefulness, based on documentation; the AI did not install or run the tool. See “Impact rating (1–5)” on the “How to read ratings & labels” page.Requirements unknown★ 1 on GitHubView website
part of contentstack/contentstack-vibe-docsby contentstack

Contentstack is where a company keeps the text and images that fill its website; this is the vendor's own manual for it, so the site gets connected the right way instead of by trial and error.

LABSCO SUMMARY

A library, not a job.

What it holds:

  • the read APIs, in REST and GraphQL form, and the write API behind them
  • image transformations, and the TypeScript delivery library
  • Live Preview and Visual Builder, in client- and server-rendered modes
  • OAuth sign-in, and the regions an account can sit in
  • Next.js, Nuxt and Gatsby, each with its own patterns

What sits at the front of it is a routing table rather than prose, so the agent reads only the pages a question needs and something this large never arrives in the conversation whole.

What it will not put in your code.

The skill also carries rules about credentials, and they are worth knowing before installing. A key is never to be printed, logged or written into the source; management tokens are server-side only and must stay out of front-end code; no token goes into git, not even in an example .env file. If a real token is pasted into the conversation, the agent is told to say so and suggest replacing it.

It is also told to ask which region and which framework are in play before writing any code, rather than assuming.

Two packages, one subject.

Contentstack also publishes Contentstack Agent Skills, a separate package of 21 task skills, and the ground they cover is nearly the same: modelling, Live Preview, webhooks, releases, workflows, branches, roles, locales and Launch turn up in both.

The difference is what each is for. That one carries a procedure per job; this one answers questions in the vendor's own words and changes nothing. Taking both is not wrong, but a lot of it would be covered twice.

WHEN TO USE

SCOPE

USE FOR

  • Build a Next.js, Nuxt or Gatsby site whose pages are filled from the content store.
  • Let editors see their changes on the real page before anyone publishes them.
  • Work out why a preview screen has gone blank or stopped updating.
  • Write a script that creates or updates hundreds of content items instead of doing it by hand.
  • Pick the right kind of access key so a browser never gets one that can change content.
  • Launch the same site in several languages and decide what shows when a translation is missing.

NOT FOR

  • Not for putting a content-editing key into browser code; the write SDK is server-only, by the author's rule.
  • Not for mixing REST and GraphQL in a single query, or the read SDK's patterns with the write SDK's.