Skip to main content
Glama
stevereiner

Alfresco MCP Server

by stevereiner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Alfresco MCP Server

No user-submitted related servers found.

    Related Servers

    • Agent Knowledge MCP

      itshare4u
      A
      license
      A
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server that integrates Elasticsearch search with file operations, document validation, and version control to transform AI assistants into powerful knowledge management systems.
      27
      93 PyPI
      27
      MIT

    • AEM MCP Server

      udaykumarbpatel
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server for Adobe Experience Manager that provides 35+ REST/JSON-RPC API methods for complete content, component, asset, and template management. Enables AI-powered AEM automation through natural language interfaces with support for page operations, component CRUD, asset management, and publishing workflows.
      MIT

    • SourceSync.ai MCP Server

      scmdr
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI models to interact with SourceSync.ai's knowledge management platform for managing documents, ingesting content from various sources, and performing semantic searches.
      25
      59 npm
      1
      ISC

    • MCP Atlassian

      uchinx
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server that integrates with Atlassian Confluence and Jira, enabling AI assistants to search, create, and update content in these platforms through natural language interactions.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 15 tools

    Disambiguation3/5

    Four search tools (search_content, advanced_search, search_by_metadata, cmis_search) have overlapping purposes and an agent could easily misselect between them, especially since advanced_search and search_by_metadata may be subsets of the AFTS search. The remaining content management tools are distinct, but the search cluster creates ambiguity.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (upload_document, create_folder, delete_node), but search tools mix conventions: advanced_search is adjective_noun, search_by_metadata uses a preposition, and cmis_search is a noun-qualified verb. Also, get_repository_info_tool has an awkward 'tool' suffix, breaking the pattern.

    Tool Count5/5

    At 15 tools, the set is within the ideal range for a domain-specific server and each tool addresses a distinct functional need (search, navigation, document operations, repository info). No tools feel redundant or unnecessary, even with multiple search variants.

    Completeness4/5

    The server covers core CRUD for nodes, search, browse, checkout/checkin, and property management. Missing operations like copy/move, document content update, and version history are minor gaps for an Alfresco integration, but the main workflows are supported without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources