Skip to main content
Glama

Servidor MCP de Contentful

Un servidor de Protocolo de Contexto de Modelo (MCP) que permite a Claude interactuar directamente con los datos de Contentful CMS. Esta integración permite a Claude obtener tipos de contenido y entradas de su espacio Contentful.

Características

  • Obtenga todos los tipos de contenido de su espacio Contentful

  • Recuperar entradas para tipos de contenido específicos

  • Respuestas estructuradas para un fácil consumo por parte de los asistentes de IA

Related MCP server: microCMS MCP Server

Prerrequisitos

  • Node.js (v16 o superior)

  • Una cuenta Contentful con claves API

  • Claude Desktop (para utilizar el servidor MCP con Claude)

Instalación

  1. Clonar este repositorio:

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

2.Instalar dependencias: npm install

Cree un archivo .env en el directorio raíz con sus credenciales de Contentful: 4. CONTENTFUL_SPACE_ID=su_id_de_espacio CONTENTFUL_ACCESS_TOKEN=su_token_de_acceso CONTENTFUL_ENVIRONMENT=develop CONTENTFUL_PREVIEW_ACCESS_TOKEN=su_token_de_vista_previa

npm ejecutar compilación

O configure un script de compilación en su package.json: "scripts": { "build": "tsc", "start": "node dist/index.js" }

##Configuración para 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