Skip to main content
Glama
dYn36

sharepoint-online-mcp

by dYn36

Related Servers

Alternatives to sharepoint-online-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      An MCP server that enables running CLI for Microsoft 365 commands through GitHub Copilot Agent, allowing users to interact with Microsoft 365 services using natural language.
      4
      932 npm
      130
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server for Microsoft Graph with delegated OAuth support, enabling interaction with Microsoft 365 services like mail, calendar, OneDrive, SharePoint, Teams, and more via natural language.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      SharePoint MCP Server is an enterprise-ready Model Context Protocol (MCP) server built with C# .NET 9. It enables local AI models (such as Ollama, Qwen, and Llama) to securely connect to Microsoft SharePoint and query document libraries, site metadata, and files via the Microsoft Graph API without exposing enterprise data to public clouds.
      MIT

    TDQS

    C2.6/5.0

    Scored across 25 tools

    Disambiguation3/5

    Clear/ambiguous split: connection and navigation tools are distinct, but multiple 'add_*' webpart tools (add_image_webpart, add_spacer, add_divider, add_text_webpart, add_custom_webpart) and section/layout tools overlap conceptually. An agent could reasonably hesitate between add_custom_webpart and the specific webpart adders, or between get_page, get_page_layout, and get_site_details.

    Naming Consistency4/5

    Predominantly consistent snake_case verb_noun convention (add_image_webpart, remove_navigation_link, get_site_details, create_page). Minor inconsistency: set_site_logo and disconnect lack the noun/object pattern, and add_spacer/add_divider omit the webpart suffix used by siblings.

    Tool Count3/5

    25 tools is at the heavy end of the acceptable range and reflects a rich domain (pages, sections, webparts, navigation, site admin, auth). However, no bulk or read-only toolset split exists and the surface feels padded with granular webpart adders rather than more general operations.

    Completeness4/5

    Covers the full page lifecycle (list, get, create, update, publish, delete) plus sections, webparts, navigation, site discovery, assets, and auth. Gaps exist: no update/delete for webparts or sections, no unpublish, no list/page-versioning, and no comment or permission management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues