Skip to main content
Glama
BrianCusack

Sharepoint MCP Server

by BrianCusack

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SITE_IDYesYour Sharepoint site ID
CLIENT_IDYesYour Microsoft client ID
TENANT_IDYesYour Microsoft tenant ID
CLIENT_SECRETYesYour Microsoft client secret
DOCKER_CONTAINERNoFlag to indicate running in Docker containertrue

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search-documentsD–

Prompts

Interactive templates invoked by user choice

NameDescription
document-summary
find-relevant-documents
explore-folder

Resources

Contextual data attached and managed by the client

NameDescription
sites
libraries

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search-documents' has a distinct purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

The naming is trivially consistent as there is only one tool. The tool name 'search-documents' follows a verb-noun pattern, which is clear and predictable, though this cannot be evaluated across multiple tools.

Tool Count2/5

A single tool is too few for a server named 'Sharepoint MCP Server', which suggests a broader domain like document management, collaboration, or file handling. This minimal set likely leaves significant gaps in functionality, making it inappropriate for the apparent scope.

Completeness1/5

The tool set is severely incomplete for a Sharepoint domain. With only a search tool, there are obvious gaps in CRUD operations (e.g., create, update, delete documents), user management, or other typical Sharepoint functionalities, which will cause agent failures in handling common workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues