Core Content Services MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCOPE | No | OAuth scope | |
| PASSWORD | No | Authentication password (required) | |
| USERNAME | No | Authentication username (required) | |
| CLIENT_ID | No | OAuth client ID | |
| TOKEN_URL | No | OAuth token URL | |
| GRANT_TYPE | No | OAuth grant type | |
| SERVER_URL | No | Content Services GraphQL API endpoint URL (required) | |
| SSL_ENABLED | No | Whether SSL is enabled. Can be set to `true`, a path to a certificate file, or `false` (not recommended for production) | true |
| OBJECT_STORE | No | Object store identifier (required) | |
| POOL_MAXSIZE | No | Maximum pool size | 100 |
| CLIENT_SECRET | No | OAuth client secret | |
| TOKEN_REFRESH | No | Token refresh interval in seconds | 1800 |
| ZENIAM_IAM_URL | No | IAM url to send user/pwd or client_id/client_secret to IAM to get back IAM token, for example: <iam_host_route>/idprovider/v1/auth/identitytoken | |
| ZENIAM_ZEN_URL | No | Zen url to send IAM token for exchange to Zen token, for example: <zen_host_route>/v1/preauth/validateAuth | |
| REQUEST_TIMEOUT | No | Request timeout in seconds | 30.0 |
| ZENIAM_IAM_USER | No | if grant type is password, specify the IAM user | |
| POOL_CONNECTIONS | No | Number of connection pool connections | 100 |
| ZENIAM_CLIENT_ID | No | if grant type is client_credentials, specify the IAM client id | |
| ZENIAM_IAM_SCOPE | No | IAM scope | |
| TOKEN_SSL_ENABLED | No | Whether SSL is enabled for token endpoint. Can be set to `true`, a path to a certificate file, or `false` (not recommended for production) | true |
| ZENIAM_IAM_PASSWORD | No | if grant type is password, specify the IAM password | |
| ZENIAM_CLIENT_SECRET | No | if grant type is client_credentials, specify the IAM client secret | |
| ZENIAM_IAM_GRANT_TYPE | No | IAM grant type | |
| ZENIAM_IAM_SSL_ENABLED | No | Whether SSL is enabled for IAM route. Can be set to `true`, a path to a certificate file, or `false` (not recommended for production) | true |
| ZENIAM_ZEN_SSL_ENABLED | No | Whether SSL is enabled for Zen exchange route. Can be set to `true`, a path to a certificate file, or `false` (not recommended for production) | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_document_versionsA | Retrieves all versions in the version series that includes the specified document. This returns all versions (past, current, and future) that belong to the same version series. |
| get_document_text_extractC | Retrieves a document's text extract content. |
| create_documentB | PREREQUISITES IN ORDER: To use this tool, you MUST call two other tools first in a specific sequence.
Description: Creates a document in the content repository with specified properties. |
| update_document_propertiesA | PREREQUISITES: Before using this tool, you MUST call ONE of these tools first:
Description: Updates an existing document's properties in the content repository. This tool ONLY updates properties and does NOT change the document's class. To change a document's class, use the update_document_class tool instead. |
| update_document_classA | PREREQUISITES: Before using this tool, you MUST call ONE of these tools first:
Description: Changes a document's class in the content repository. WARNING: Changing a document's class can result in loss of properties if the new class does not have the same properties as the old class. Properties that don't exist in the new class will be removed from the document. This tool ONLY changes the document's class and does NOT update any properties. To update properties after changing the class, use the update_document_properties tool. |
| checkin_documentC | Checks in a document in the content repository with specified properties. |
| checkout_documentC | Checks out a document in the content repository. |
| delete_version_seriesA | Deletes an entire version series (all versions of a document) in the content repository. |
| delete_document_versionC | Deletes a specific document version in the content repository. |
| get_document_propertiesA | Retrieves a document's properties from the content repository by ID or path. Note: Use this tool ONLY when you need to retrieve a document using its ID or file path. For searching documents by other properties, use the repository_search tool instead. |
| cancel_document_checkoutA | Cancels a document checkout in the content repository. |
| document_searchA | PREREQUISITES IN ORDER: To use this tool, you MUST call two other tools first in a specific sequence.
Description: This tool will execute a request to search for documents based on content and the metadata criteria. |
| create_folderB | PREREQUISITES IN ORDER: To use this tool, you MUST call two other tools first in a specific sequence.
Creates a folder in the content repository with specified properties. This tool interfaces with the GraphQL API to create a new folder object with the provided parameters. |
| delete_folderB | Deletes a folder in the content repository. This tool interfaces with the GraphQL API to delete a folder object with the provided id. :param identifier string Yes The unique identifier or path for the folder. If not provided, an error will be returned. :returns: If successful, return the folder id. Else, return a ToolError instance that describes the error. |
| unfile_documentA | Unfile a document from a folder in the content repository. This tool interfaces with the GraphQL API to unfile document from folder with the provided ids. :param folder_id_or_path string Yes The unique identifier or path for the folder. If not provided, an error will be returned. :param document_id string Yes The unique identifier for the document. If not provided, an error will be returned. :returns: If successful, return the folder id. Else, return a ToolError instance that describes the error. |
| file_documentA | File a document to a folder in the content repository. This tool interfaces with the GraphQL API to create a referential containment relationship between a document and a folder. :param document_id_or_path string Yes The unique identifier or path for the document. :param folder_id_or_path string Yes The unique identifier or path for the folder. :returns: If successful, returns the reference containment relationship ID Else, return a ToolError instance that describes the error. |
| update_folderA | PREREQUISITES IN ORDER: To use this tool, you MUST call two other tools first in a specific sequence.
Description: Updates an existing folder in the content repository with specified properties. |
| get_folder_documentsB | Retrieves a folder's contained documents. |
| get_folder_detailB | Description: Get an existing folder in the content repository information given a folder id |
| list_root_classesA | List all available root class types in the repository. This tool should be called first to get a list of valid root class names before using the list_all_classes tool. :returns: A list of all available root class types (e.g., ["Document", "Folder", "Annotation", "CustomObject"]) |
| determine_classA | Find classes that match the given keywords by looking for substring matches in class names and descriptions. IMPORTANT:
To get a list of all valid class names that can be used with this tool, you MUST first call the |
| get_class_property_descriptionsA | Retrieves ALL properties of a class including system properties. IMPORTANT: Use this tool ONLY for general document updates where you need to see ALL properties of a class, including system-owned and hidden properties. DO NOT use this tool for property extraction workflows. |
| get_searchable_property_descriptionsA | Retrieves only the searchable properties of a class. |
| repository_object_searchB | PREREQUISITES IN ORDER: To use this tool, you MUST call two other tools first in a specific sequence.
Description: This tool retrieves repository objects other than Document instances. |
| lookup_documents_by_nameD | – |
| lookup_documents_by_pathB | PREREQUISITE: To use this tool, you MUST call the determine_class tool first to get the class_symbolic_name. If the user does not specify a specific clas then call determine_class with the root Document class. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Most tools map to a distinct resource+action (create/update/delete for documents and folders, versioning, classification), but the retrieval surface is muddled: get_document_properties (accepts id OR path), lookup_documents_by_name, lookup_documents_by_path, and document_search all retrieve documents and could easily be confused. The class-related tools (list_root_classes, determine_class, get_class_property_descriptions, get_searchable_property_descriptions) are reasonably distinct but require careful reading of prerequisite notes.
Mostly consistent snake_case verb_noun pattern (create_document, update_folder, delete_folder, get_folder_documents), but there are noun_verb deviations (document_search, repository_object_search) that break the pattern. Single-word bare verbs like determine_class and the checkin_document/checkout_document verbs also deviate slightly from the dominant get_/create_/update_/delete_ convention.
At 26 tools this is on the heavy side, and the domain (documents, folders, versioning, classification, search) is broad enough to justify much of it. However, some redundancy (three-plus overlapping document-retrieval tools) suggests the set is larger than strictly necessary.
Strong lifecycle coverage: full CRUD for documents and folders, versioning (checkin/checkout/cancel/delete versions), classification/metadata, file/unfile relationships, and both document and object search. Minor gaps remain—no annotation tools despite list_root_classes advertising Annotation, and no move/copy operations—but core workflows are well covered.