Skip to main content
Glama
icemage001

SharePoint MCP Bridge

by icemage001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to SharePoint MCP Bridge

No user-submitted related servers found.

    Related Servers

    • newton-browser

      Koala-Studios
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for local browser control via Chrome/Edge extension, enabling agents to open isolated tabs, observe pages, take screenshots, and interact with accessible controls using an existing browser profile. It is agent-agnostic, local-only, and supports safe session scoping with origin grants and sensitive-data blocking.
      MIT

    • msloop-mcp

      shayanline
      A
      license
      A
      quality
      F
      maintenance
      MCP server that provides read access to Microsoft Loop workspaces and pages by reusing your Loop web session, enabling listing, reading, and searching across Loop content without app registration.
      8
      20 npm
      2
      MIT

    • Intune Assignment Checker MCP

      ugurkocde
      A
      license
      A
      quality
      A
      maintenance
      A local, read-only MCP server that inspects and explains Microsoft Intune assignments through Microsoft Graph /beta, with delegated sign-in and secure token caching.
      6
      17 npm
      3
      MIT

    • patchright-mcp

      quantmew
      A
      license
      Not graded
      quality
      D
      maintenance
      A MCP server based on Patchright that enables browser automation with session inheritance from local Chrome/Edge/Chromium browsers, including cross-platform cookie decryption.
      348 npm
      3
      Apache 2.0
    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.7/5.0

    Scored across 75 tools

    Disambiguation4/5

    Tools are generally distinct by resource and action, with clear naming like list_lists vs get_list, and preview/apply pairs clearly separated. The large number of similar preview/apply operations across different resources (lists, items, columns, views, permissions, groups, pages) could cause some confusion, but descriptions and naming help disambiguate.

    Naming Consistency4/5

    The majority of tool names follow a consistent verb_noun snake_case pattern (e.g., list_items, create_column, apply_view_update). Minor deviations such as 'download_file_metadata' and 'ensure_site_user' break the pure verb_noun flow but are still readable and predictable. Overall the pattern is strong.

    Tool Count2/5

    With 75 tools, the count is well above the 25+ threshold, making the surface feel heavy. Many tools exist as preview/apply pairs, effectively doubling the count for a single logical operation. While the domain is broad, the tool count is excessive and could overwhelm agents.

    Completeness4/5

    The tool set covers CRUD for lists, items, columns, views, groups, and drives, plus permissions, pages, formatting, and site management. Minor gaps exist such as no page deletion, no drive file content download, and no site creation, but these are workable and do not force dead ends in typical workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources