Contentful MCP Server provides a comprehensive interface for managing Contentful content via the MCP protocol. It exposes tools for entry management (search, create, retrieve, update, delete, publish, unpublish), asset handling (upload, list, get, update, delete, publish, unpublish), content types, spaces and environments, localization, and bulk operations like bulk_publish, bulk_unpublish, and bulk_validate. The server also includes an MCP Inspector for development and testing, offering a visual interface to try tools and view responses in real time. To use it with Claude Desktop or other MCP clients, configure the server in your client settings and invoke the available tools to perform operations against your Contentful spaces and environments. When listing assets or entries, the server enforces a 3-item per page limit to prevent context window overflow, while returning pagination metadata to fetch subsequent pages as needed.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your machine
• Git for cloning the repository

Installation steps:

1. Clone the repository git clone https://github.com/ivotoby/ivo-toby-contentful-mcp-server.git cd ivo-toby-contentful-mcp-server

2. Install dependencies npm install

3. Configure environment variables Create a .env file or export variables in your shell. Required variables include:

   • CONTENTFUL_HOST (default: https://api.contentful.com)
   • CONTENTFUL_MANAGEMENT_ACCESS_TOKEN (CM API token) Optional aliases can be used as arguments if supported by the server.

4. Run the MCP server (development) npm run dev

   or start in production mode if configured

5. Verify startup The server should be listening on the HTTP port configured by HTTP_PORT (default 3000) and accessible via the host defined by HTTP_HOST.

Notes and tips:

• Ensure your Contentful API token has the necessary permissions for the operations you plan to perform.
• If you do not need the HTTP server feature, you can disable ENABLE_HTTP_SERVER to avoid opening ports.
• The MCP Inspector tool can be accessed at http://localhost:5173 when using npm run inspect or npm run inspect:watch.
• For large migrations, leverage bulk operations (bulk_publish, bulk_unpublish, bulk_validate) to minimize API calls and track progress via status updates.
• When using threaded comments to manage content discussions, you can create replies by passing a parent comment ID in create_comment to build a conversation tree.
• If you encounter authentication issues, double-check the CONTENTFUL_MANAGEMENT_ACCESS_TOKEN and ensure there are no token expirations or scope restrictions.