Contentstack MCP Streamable MCP Server

1

Add it to Claude Code

Run this in a terminal.

Run in terminal
claude mcp add --transport http contentstack-mcp-streamable http://localhost:3000/mcp
Required:CONTENTSTACK_API_KEY+ 7 optional
README.md

A transport wrapper that exposes Contentstack MCP tools over HTTP

Contentstack MCP Streamable HTTP Server

DEPRECATED: Contentstack will build a Streamable http server soon

A Streamable HTTP transport wrapper for the @contentstack/mcp package. This server exposes all Contentstack MCP tools over HTTP instead of stdio, enabling remote access, horizontal scaling, and integration with browser-based and networked MCP clients.

How It Works

This server acts as a transparent proxy:

  1. Spawns @contentstack/mcp as a child process communicating via stdio
  2. Discovers all available tools from the child process
  3. Exposes them over Streamable HTTP transport at a single /mcp endpoint
  4. Forwards tool calls from HTTP clients to the underlying Contentstack MCP server

All tools from @contentstack/mcp are available — CMA, CDA, Analytics, BrandKit, Launch, DeveloperHub, Lytics, and Personalize.

Prerequisites

  • Node.js 18+
  • A Contentstack account with appropriate credentials
  • OAuth authentication completed (for CMA, Analytics, BrandKit, Launch, DeveloperHub, Personalize)

Setup

1. Install dependencies

npm install

2. Configure environment variables

Copy the example env file and fill in your credentials:

cp .env.example .env

Edit .env with your Contentstack credentials:

CONTENTSTACK_API_KEY=your_stack_api_key
GROUPS=cma

See Environment Variables for the full list.

3. Authenticate with OAuth

Before using CMA, Analytics, BrandKit, Launch, DeveloperHub, or Personalize tools, run the OAuth flow:

npm run auth

This stores your OAuth tokens locally for the child process to use.

4. Build and run

npm run build
npm start

For development with auto-reload:

npm run dev

The server starts on port 3000 by default.

Connecting a Client

Configure your MCP client to connect via Streamable HTTP. Example mcp-config.json:

{
  "mcpServers": {
    "contentstack": {
      "type": "streamable-http",
      "url": "http://localhost:3000/mcp"
    }
  }
}

Cursor IDE

Add to your Cursor MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "contentstack": {
      "type": "streamable-http",
      "url": "http://localhost:3000/mcp"
    }
  }
}

Environment Variables

Variable Required Description
PORT No Server port (default: 3000)
CONTENTSTACK_API_KEY Yes Your Stack API Key
CONTENTSTACK_DELIVERY_TOKEN CDA only Delivery token for Content Delivery API
CONTENTSTACK_BRAND_KIT_ID BrandKit only Brand Kit ID
CONTENTSTACK_LAUNCH_PROJECT_ID Launch only Launch Project ID
CONTENTSTACK_PERSONALIZE_PROJECT_ID Personalize only Personalize Project ID
LYTICS_ACCESS_TOKEN Lytics only Lytics access token
GROUPS No Comma-separated API groups to enable (default: cma). Options: cma, cda, analytics, brandkit, launch, developerhub, lytics, personalize, all

API Groups

Group Authentication Required Configuration
CMA OAuth Stack API Key
CDA Token-based Stack API Key + Delivery Token
Analytics OAuth Stack API Key
BrandKit OAuth Stack API Key + Brand Kit ID
Launch OAuth Stack API Key + Launch Project ID
DeveloperHub OAuth Stack API Key
Lytics Token-based Lytics Access Token
Personalize OAuth Stack API Key + Personalize Project ID

Endpoints

Method Path Description
POST /mcp MCP JSON-RPC requests (initialize, tool calls)
GET /mcp SSE stream for server-to-client notifications
DELETE /mcp Session termination
GET /health Health check with tool count and active sessions

License

MIT

Environment Variables

PORTServer port (default: 3000)
CONTENTSTACK_API_KEYrequiredYour Stack API Key
CONTENTSTACK_DELIVERY_TOKENDelivery token for Content Delivery API
CONTENTSTACK_BRAND_KIT_IDBrand Kit ID
CONTENTSTACK_LAUNCH_PROJECT_IDLaunch Project ID
CONTENTSTACK_PERSONALIZE_PROJECT_IDPersonalize Project ID
LYTICS_ACCESS_TOKENLytics access token
GROUPSComma-separated API groups to enable (cma, cda, analytics, etc.)

Configuration

claude_desktop_config.json
{"mcpServers": {"contentstack": {"type": "streamable-http", "url": "http://localhost:3000/mcp"}}}

Try it

Fetch the latest content entries from my Contentstack stack using the CMA tools.
List all available projects in my Contentstack Launch environment.
Retrieve analytics data for my content entries using the Contentstack Analytics API.
Update the brand assets in my Contentstack BrandKit project.

Frequently Asked Questions

What are the key features of Contentstack MCP Streamable?

Exposes Contentstack MCP tools over HTTP instead of stdio. Enables remote access and horizontal scaling for MCP clients. Supports multiple API groups including CMA, CDA, Analytics, and Launch. Provides a transparent proxy for browser-based and networked MCP clients. Includes a health check endpoint for monitoring server status.

What can I use Contentstack MCP Streamable for?

Integrating Contentstack CMS management into browser-based AI development environments. Scaling Contentstack MCP tool access across multiple networked client instances. Managing Contentstack content and assets remotely from non-local MCP clients. Automating Contentstack workflows across different projects like Launch and Personalize.

How do I install Contentstack MCP Streamable?

Install Contentstack MCP Streamable by running: npm install && npm run build && npm start

What MCP clients work with Contentstack MCP Streamable?

Contentstack MCP Streamable works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep Contentstack MCP Streamable docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Need the old visual installer? Open Conare IDE.
Open Conare