Core Content Services MCP Server
OfficialRelated Servers
Alternatives to Core Content Services MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI models to interact with IBM FileNet Content Manager for document lifecycle management, metadata extraction, legal holds, and AI-powered search, summaries, and Q\&A.26Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI models to access IBM FileNet Content Manager capabilities including document management, property extraction, legal holds, and AI-powered document insight through standardized MCP interfaces.30Apache 2.0

OpenPages Local MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceEnables AI agents to securely interact with IBM OpenPages GRC platform through a standardized interface, supporting CRUD operations on objects like issues and controls.8Apache 2.0- AlicenseAqualityAmaintenanceEnables AI assistants to search, read, and manage documents in a Laserfiche repository via the MCP protocol, with optional write operations and safety controls.382MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to manage Microsoft SharePoint documents and folders through natural language, supporting operations like listing, reading, uploading, updating, deleting, and creating Office files.13MIT

Watsonx.data Document Libraryofficial
AlicenseNot gradedqualityCmaintenanceBridges AI agents with watsonx.data document libraries, enabling natural language queries and intelligent retrieval from document libraries.4Apache 2.0
TDQS
Scored across 26 tools
Most tools are distinct, but there is notable overlap between the various search/lookup tools (lookup_documents_by_name, lookup_documents_by_path, document_search, repository_object_search) and between get_document_properties vs get_document_versions vs get_document_text_extract. The descriptions help clarify some boundaries, but an agent could easily confuse which search tool to use.
Tool names mostly follow a consistent verb_noun pattern (get_document_properties, create_document, update_document_properties, delete_folder, checkout_document). Minor deviations exist: repository_object_search and lookup_documents_by_name/path use different verb styles, and get_folder_detail breaks the pattern slightly.
26 tools is on the heavy side for a content services server, but the domain is broad (documents, folders, classes, search, versioning, check-in/out). It feels slightly over-scoped, with several overlapping search tools that could be consolidated.
The tool surface covers document CRUD, versioning, check-in/out, folder management, classification, and search. Minor gaps exist: there is no explicit get_folder_children or list_folder_contents beyond get_folder_documents, and no tool to move/copy documents between folders, but core workflows are covered.