in the specified branch, assigning a new name and optional description to the cloned release. - **add_items_to_a_release**: This tool programmatically adds specified content items to a designated release within a Contentstack stack branch by accepting structured item data in JSON format, enabling automated release management and deployment workflows. - **delete_items_from_a_release**: This tool programmatically removes specified content items from a designated release within a Contentstack stack branch, requiring the release identifier and item data in JSON format for precise targeting and execution. - **deploy_a_release**: This tool deploys a specified release to one or more target environments within a Contentstack stack, supporting branch selection and optional scheduling for automated release publishing. ### Publishing Management - **get_publish_queue**: This tool retrieves metadata and content for all entries, both published and unpublished, within a specified stack branch, supporting query filtering, pagination, and branch selection. ## Configuration ### Prerequisites 1. Create a Contentstack account at [Contentstack](https://www.contentstack.com/login/) 2. Generate a [Management token](https://www.contentstack.com/docs/developers/create-tokens/generate-a-management-token/) from your Stack Settings 3. For Content Delivery API access, generate a [Delivery token](https://www.contentstack.com/docs/developers/create-tokens/create-a-delivery-token/) for the appropriate environment ### Environment Variables These variables can also be set as arguments - `CONTENTSTACK_REGION` / `--region`: Contentstack Regions (defaults to NA) - Possible values: `NA` (for AWS NA), `EU` (for AWS EU), `AZURE_NA`, `AZURE_EU`, `GCP_NA`, `GCP_EU` - `CONTENTSTACK_API_KEY` / `--stack-api-key`: Your Stack API Key - `CONTENTSTACK_MANAGEMENT_TOKEN` / `--management-token`: Your Stack Management token - `CONTENTSTACK_DELIVERY_TOKEN` / `--delivery-token`: Your Stack Delivery token (required only if using CDN/Delivery API tools) ### Usage with Claude Desktop You can use this MCP without cloning the repository by simply modifying your Claude Desktop configuration file. Just edit `~/Library/Application Support/Claude/claude_desktop_config.json` to include the necessary configuration. ```json { "mcpServers": { "contentstack": { "command": "npx", "args": ["-y", "@contentstack/mcp"], "env": { "CONTENTSTACK_API_KEY": "", "CONTENTSTACK_MANAGEMENT_TOKEN": "", "CONTENTSTACK_REGION": "", "CONTENTSTACK_DELIVERY_TOKEN": "" } } } } ``` Note: The `CONTENTSTACK_DELIVERY_TOKEN` is optional and only required if you plan to use the Content Delivery API (CDN) tools. If your MCPClient doesn't support environment variables, you can alternatively provide the required authentication parameters as command-line arguments: ```json { "mcpServers": { "contentstack": { "command": "npx", "args": [ "-y", "@contentstack/mcp", "--management-token", "", "--stack-api-key", "", "--region", "", "--delivery-token", "" ] } } } ``` ### Developing and using Claude desktop If you want to contribute and test what Claude does with your contributions; - run `npm run dev`, this will start the watcher that rebuilds the MCP server on every change - update `claude_desktop_config.json` to reference the project directly, ie; ```json { "mcpServers": { "contentful": { "command": "node", "args": ["/path/to/mcp/bin/contentstack-mcp.js"], "env": { "CONTENTSTACK_API_KEY": "", "CONTENTSTACK_MANAGEMENT_TOKEN": "", "CONTENTSTACK_REGION": "", "CONTENTSTACK_DELIVERY_TOKEN": "" } } } } ```

Contentstack MCP Server

评论