Contentstack
Manage Contentstack entries, assets, releases, webhooks and publishing through the Content Management API.
About
Contentstack ships in the w6w first-party pack. It declares 34 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.contentstack- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Content Management · Developer Tools
Overview
Contentstack is a headless, API-first content management system. This app exposes its Content Management API (CMA) to a workflow, authenticated with a stack API key and a management token.
A workflow can read content types, global fields, locales, environments and branches, list and fetch entries and assets, and create, update and delete entries. It can publish and unpublish entries and assets to environments and locales immediately or on a schedule, publish or unpublish up to ten items at a time in bulk and follow the resulting job, move an entry through a workflow stage, build and deploy releases, and manage webhooks that notify other systems when content changes.
A stack lives in one of seven regions (AWS North America, Europe and Australia, Azure North America and Europe, GCP North America and Europe), each on its own API host; the region is chosen once on the connection and only those seven hosts are ever called. The Content Management API is rate limited to ten requests per second per organization (one per second for bulk actions), and the action descriptions call out the per-request item limits.
Build with Contentstack
Three routes to the same 34 actions. The Workflow tab is generated from Contentstack's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Bulk Publish
bulk-publish Publish up to 10 entries and assets to environments in one request (1 request per second).
Bulk Unpublish
bulk-unpublish Unpublish up to 10 entries and assets from environments in one request.
Create Webhook
create-webhook Create a webhook that posts to a URL (no authentication) when the listed events fire.
List Content Types
list-content-types Content types in the stack (the API returns up to 100 per call).
List Entries
list-entries Entries of a content type (the API returns up to 100 per call; page with skip).
Unpublish Entry
unpublish-entry Unpublish an entry from environments and locales, now or on a schedule.
Update Entry
update-entry Update fields of an entry. Send the whole set of fields to change; unset fields keep their value.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Contentstack's real ids.
{
"manifestVersion": "2",
"name": "contentstack-example",
"steps": [
{
"id": "add-release-item",
"uses": {
"app": "io.w6w.contentstack",
"action": "add-release-item",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"releaseUid": "<releaseUid>",
"uid": "<uid>",
"contentTypeUid": "<contentTypeUid>"
}
}
]
}Here are some of the things you can do
-
Add Item to Release
performadd-release-item -
Bulk Publish
performbulk-publish -
Bulk Unpublish
performbulk-unpublish -
Create Entry
performcreate-entry -
Create Release
performcreate-release
+29 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Contentstack, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Contentstack. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "add-release-item",
payload: {
releaseUid: "<value>",
uid: "<value>",
contentTypeUid: "<value>",
// version: "<value>",
action: "<value>",
// locale: "<value>",
// branch: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action add-release-item --payload '{"releaseUid":"<value>","uid":"<value>","contentTypeUid":"<value>","action":"<value>"}'Give an AI agent Contentstack — without giving it Contentstack's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.contentstack#add-release-item",
"input": {
"releaseUid": "<releaseUid>",
"uid": "<uid>",
"contentTypeUid": "<contentTypeUid>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Contentstack connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Contentstack's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Contentstack itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Contentstack declares its own checks, so its health is a property of the app rather than something the host guesses at.
Contentstack platform status
The Content Management API component for THIS connection's region on status.contentstack.com. Reads the Connection for the region; sends no credential.