dms-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DMS_BRIDGE_URL | No | Local bridge URL | http://127.0.0.1:8765 |
| DMS_BROKER_URL | No | Local broker URL | http://127.0.0.1:8776 |
| DMS_MCP_TIMEOUT_SECONDS | No | Upstream HTTP timeout | 30 |
| DMS_MCP_USER_CONFIG_DIR | No | Directory for user configuration | |
| DMS_MCP_MACHINE_CONFIG_DIR | No | Directory for machine configuration | |
| DMS_MCP_MAX_DOCUMENT_BYTES | No | Maximum document returned to MCP | 1048576 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_healthA | Check whether the local DMS Provider Bridge is available. |
| list_connectionsA | List DMS connections available through the bridge. |
| list_itemsB | List files and folders at a connection:/path location. |
| search_itemsA | Search natively below connection:/path. Returned paths are exact and must be reused verbatim; never shorten or rewrite them. By default return unique files only. |
| open_share_urlA | Open an Alfresco or eDoCat DMS share URL read-only. Resolve its exact path, return item metadata, and list contents when it targets a folder. |
| get_item_infoA | Return metadata for one file or folder at connection:/path. |
| read_documentA | Read a size-limited document; text is decoded and binary data is base64 encoded. |
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 7 tools
Each tool has a clearly distinct purpose: health check, connection listing, item listing, search, share URL resolution, metadata retrieval, and document reading. There is no overlapping functionality that would cause confusion.
Most tools follow a verb_noun pattern (list_connections, list_items, search_items, open_share_url, get_item_info, read_document), but bridge_health deviates by using a noun phrase. The inconsistency is minor and does not impede readability.
With 7 tools, the server is well-scoped for a DMS read-access bridge. Each tool serves a necessary function, and the count falls comfortably within the ideal range.
The server comprehensively covers browsing, searching, metadata retrieval, and document content access. However, it lacks any write operations (create, update, delete), which may limit functionality if full DMS management is expected. For read-only access, it is nearly complete.