Skip to main content
Glama

Contentful MCP Server

A Model Context Protocol (MCP) server that allows Claude to interact with Contentful CMS data directly. This integration enables Claude to fetch content types and entries from your Contentful space.

Features

  • Fetch all content types from your Contentful space

  • Retrieve entries for specific content types

  • Structured responses for easy consumption by AI assistants

Related MCP server: microCMS MCP Server

Prerequisites

  • Node.js (v16 or higher)

  • A Contentful account with API keys

  • Claude Desktop (to use the MCP server with Claude)

Installation

  1. Clone this repository:

    git clone https://github.com/yourusername/contentful-mcp-server.git
    cd contentful-mcp-server

2.Install dependencies: npm install

Create a .env file in the root directory with your Contentful credentials: 4. CONTENTFUL_SPACE_ID=your_space_id CONTENTFUL_ACCESS_TOKEN=your_access_token CONTENTFUL_ENVIRONMENT=develop CONTENTFUL_PREVIEW_ACCESS_TOKEN=your_preview_token

npm run build

Or configure a build script in your package.json: "scripts": { "build": "tsc", "start": "node dist/index.js" }

##Configuration for Claude Desktop

{
  "mcpServers": {
    "contentful": {
      "command": "node",
      "args": [
        "/absolute/path/to/contentful-mcp-server/dist/index.js"
      ]
    }
  }
}

Available Tools

2 tools
get-content-typesC

get content types

Inputs: no named parameters.

get-entriesC

Get entries for a specific content type

Inputs: contentType (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get-content-types retrieves metadata about content types, while get-entries fetches actual content entries for a specific type. There is no overlap or ambiguity between these operations.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern with hyphens (get-content-types and get-entries). The naming is predictable and uniform across the set.

    Tool Count2/5

    With only 2 tools, the server feels severely under-scoped for a Contentful MCP server, which typically involves content management operations like creating, updating, or deleting entries and content types. This minimal set limits functionality.

    Completeness2/5

    The toolset is significantly incomplete for a content management domain. It only provides read operations (get-content-types and get-entries), missing essential CRUD operations such as create, update, or delete for entries and content types, which are core to content management workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers