Skip to main content
Glama

Contentful MCP-Server

Ein Model Context Protocol (MCP)-Server ermöglicht Claude die direkte Interaktion mit Contentful CMS-Daten. Durch diese Integration kann Claude Inhaltstypen und Einträge aus Ihrem Contentful-Bereich abrufen.

Merkmale

  • Holen Sie sich alle Inhaltstypen aus Ihrem Contentful-Bereich

  • Abrufen von Einträgen für bestimmte Inhaltstypen

  • Strukturierte Antworten zur einfachen Nutzung durch KI-Assistenten

Related MCP server: microCMS MCP Server

Voraussetzungen

  • Node.js (v16 oder höher)

  • Ein Contentful-Konto mit API-Schlüsseln

  • Claude Desktop (um den MCP-Server mit Claude zu verwenden)

Installation

  1. Klonen Sie dieses Repository:

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

2.Abhängigkeiten installieren: npm install

Erstellen Sie eine .env-Datei im Stammverzeichnis mit Ihren Contentful-Anmeldeinformationen: 4. CONTENTFUL_SPACE_ID=Ihre_Space-ID CONTENTFUL_ACCESS_TOKEN=Ihr_Zugriffstoken CONTENTFUL_ENVIRONMENT=develop CONTENTFUL_PREVIEW_ACCESS_TOKEN=Ihr_Vorschautoken

npm run build

Oder konfigurieren Sie ein Build-Skript in Ihrem package.json: "scripts": { "build": "tsc", "start": "node dist/index.js" }

##Konfiguration für 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