| FMRS | 58 / 100 · C | 61 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 10 / 20 | 13 / 20 |
|---|
| Maintenance | 12 / 20 | 10 / 20 |
|---|
| Documentation | 15 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Developers using Claude Desktop or other MCP clients to manage Contentful content.
- Teams needing to automate content publishing, batch updates, or validation.
- Non-technical users who want to interact with Contentful content through a chat interface.
| - Developers who want to integrate Microsoft 365 data into AI assistants or custom applications.
- Scenarios requiring unified access across multiple services (email, calendar, files, Teams, etc.).
- Lightweight solutions to interact with Graph API via MCP protocol.
|
|---|
| Not for | - Users requiring official support (this server is community-driven, not officially supported by Contentful).
- Scenarios needing to list more than 3 items per page without pagination.
- Users who cannot provide a management token (unless using App Identity authentication).
| - Highly secure enterprise production environments (requires careful scope management and deployment complexity).
- Admin tasks requiring Microsoft 365 admin permissions (like security alerts, audit logs) — consider companion project ms-365-admin-mcp-server.
- Environments without Node.js.
- Support for non-Microsoft clouds like GCC High (only Global and China 21Vianet currently).
|
|---|
| Required permissions | - Contentful Management API token with read and write permissions for content, spaces, environments, content types, etc.
- Ability to create, update, delete, publish, and unpublish entries and assets.
- Ability to create, update, and delete comments.
- Ability to create and delete environments.
- Ability to modify content type definitions.
| - Requires Microsoft Graph API permissions, dynamically requested based on enabled tools. Examples: User.Read, Mail.Read, Files.Read.
- Organization mode (--org-mode) requires additional Graph permissions for Teams, SharePoint, etc. (e.g., Sites.Read.All).
- Shared mailbox access requires delegated Mail.Read.Shared or Mail.Send.Shared scopes.
- Use --allowed-scopes to restrict tool exposure; --extra-scopes to add extra scopes. Note: --allowed-scopes only narrows, never expands permissions.
|
|---|
| Risks and side effects | - This MCP server allows AI agents to update, delete content, spaces, and content models, which could lead to accidental data loss or modification.
- Exposure of the management token could lead to unauthorized access.
- Community server may be less stable or secure than an official one.
| - Token security: File-based token storage may be exposed; use OS credential storage or secure custom paths.
- Overly broad permissions: default requests all scopes implied by tools; use allowed-scopes or tool filtering to limit.
- Multi-tenant token risk: With default 'common' tenant, personal account refresh tokens may be rejected as of June 2026, causing session expiry.
- Third-party project risk: Not officially maintained, potentially less stable than official solutions.
- HTTP mode OAuth setup complexity: Requires correct Azure AD app registration and redirect URIs.
|
|---|
| Supported clients | Claude Desktop | Claude Desktop, Open WebUI |
|---|
| Tools | 33 | 10 |
|---|