Skip to main content
Glama
box-community

MCP Server Box

by box-community
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP Server Box

No user-submitted related servers found.

    Related Servers

    • Box MCP Server

      SaiyemRaiyan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Box files, folders, collaborations, and more via the Box API using tools for search, upload, and metadata operations.
      10 npm
      ISC

    • Alfresco MCP Server

      stevereiner
      A
      license
      B
      quality
      B
      maintenance
      Python-based server that provides AI-native access to Alfresco content management operations through the Model Context Protocol, enabling search, document lifecycle management, version control, and other content operations.
      15
      14
      Apache 2.0

    • Document Q&A MCP Server

      SY-MR-CODER
      A
      license
      Not graded
      quality
      D
      maintenance
      A Python-based MCP server that enables document-based question answering by processing PDF, TXT, and Markdown files through OpenAI's API. It provides hallucination-free responses based strictly on document content using semantic search and includes a web interface for management.
      MIT

    • Vibe Model Context Protocol

      non-npc
      A
      license
      Not graded
      quality
      D
      maintenance
      A Python-based server for managing and analyzing code context for AI-assisted development. Provides real-time code analysis, project structure analysis, dependency tracking, and secure API endpoints.
      15
      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

    B3.1/5.0

    Scored across 117 tools

    Disambiguation3/5

    Most tools have distinct purposes within their categories, but there is significant overlap in the AI extraction tools (e.g., box_ai_extract_freeform_tool vs. box_ai_extract_structured_using_fields_tool) and collaboration tools (multiple variations for files/folders with users/groups). The descriptions help differentiate them, but the sheer number of similar tools could cause confusion for an agent trying to select the right one.

    Naming Consistency4/5

    The naming follows a consistent snake_case pattern with a clear prefix (box_) and resource-action structure (e.g., box_file_download_tool, box_folder_create_tool). Minor deviations exist, such as box_who_am_i (no '_tool' suffix) and mcp_server_info (different prefix), but overall the convention is predictable and readable.

    Tool Count2/5

    With 117 tools, the count is excessive for a single server, even for a comprehensive Box API integration. This many tools will overwhelm agents and make navigation difficult. The scope is broad, but the tool set feels bloated with many fine-grained variations (e.g., separate collaboration tools for files/folders by user ID, login, or group ID) that could be consolidated.

    Completeness5/5

    The tool set provides extensive coverage of the Box domain, including files, folders, collaborations, metadata, AI features, tasks, shared links, users, groups, and document generation. It supports full CRUD operations and lifecycle management across all major resources, with no apparent gaps that would hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources