조직 SharePoint에 대한 액세스를 제공하는 모델 컨텍스트 프로토콜 서버입니다.
요소 | 작업 | 의지 | 동적 리소스 | 도구 |
사용자 | ❌ | ❌ | ❌ | |
사용자 읽기 | ❌ | ❌ | ❌ | |
사용자 찾기 | ❌ | ❌ | ❌ | |
사이트 | ❌ | ❌ | ❌ | |
사이트 목록 | ✅ | ❌ | ❌ | |
사이트 세부 정보 가져오기 | ❌ | ❌ | ❌ | |
하위 사이트 만들기 | ❌ | ❌ | ❌ | |
사이트 삭제 | ❌ | ❌ | ❌ | |
드라이브 | ❌ | ❌ | ❌ | |
폴더 목록 | ❌ | ❌ | ❌ | |
폴더 검색 | ❌ | ❌ | ✅ | |
폴더 만들기 | ❌ | ❌ | ❌ | |
폴더 삭제 | ❌ | ❌ | ❌ | |
파일 업로드 | ❌ | ❌ | ❌ | |
목록 항목 | ❌ | ✅ | ❌ | |
파일 다운로드 | ❌ | ❌ | ✅ | |
파일 읽기 | ✅ | ❌ | ❌ | |
파일 이동 | ❌ | ❌ | ❌ | |
파일 복사 | ❌ | ❌ | ❌ | |
기울기 | ❌ | ❌ | ❌ | |
목록 만들기 | ❌ | ❌ | ❌ | |
읽기 목록 | ❌ | ❌ | ❌ | |
목록에 추가 | ❌ | ❌ | ❌ | |
업데이트 목록 | ❌ | ❌ | ❌ | |
목록 삭제 | ❌ | ❌ | ❌ | |
달력 | ❌ | ❌ | ❌ | |
이벤트 만들기 | ❌ | ❌ | ❌ | |
이벤트 읽기 | ❌ | ❌ | ❌ | |
이벤트 업데이트 | ❌ | ❌ | ❌ | |
이벤트 삭제 | ❌ | ❌ | ❌ |
문서 요약
관련 문서 찾기
탐색-폴더
Related MCP server: SharePoint MCP Server
.env.example을 .env로 복사합니다.
필수 필드를 채우세요
루트에서
지엑스피1
Claude Desktop 앱과 함께 이 서버를 사용하려면 claude_desktop_config.json 의 "mcpServers" 섹션에 다음 구성을 추가하세요.
Docker 빌드 및 태그 docker build -t mcp/sharepoint .
{
"mcpServers": {
"sharepoint": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e", "DOCKER_CONTAINER=true",
"-e", "TENANT_ID=your-tenant-id",
"-e", "CLIENT_ID=your-client-id",
"-e", "CLIENT_SECRET=your-client-secret",
"-e", "SITE_ID=your-site-id",
"-e", "DRIVE_ID=your-drive-id",
"mcp/sharepoint"
]
}
}
}pnpm run build{
"mcpServers": {
"sharepoint": {
"command": "node",
"args": ["run", "start"],
"env": {
"TENANT_ID": "your-tenant-id",
"CLIENT_ID": "your-client-id",
"CLIENT_SECRET": "your-client-secret",
"SITE_ID": "your-site-id",
"DRIVE_ID": "your-drive-id",
}
}
}
}이 MCP 서버는 MIT 라이선스에 따라 라이선스가 부여됩니다. 즉, MIT 라이선스의 조건에 따라 소프트웨어를 자유롭게 사용, 수정 및 배포할 수 있습니다. 자세한 내용은 프로젝트 저장소의 LICENSE 파일을 참조하세요.
| Name | Required | Description | Default |
|---|---|---|---|
| maxResults | No | Maximum number of results to return (as a string) | |
| query | Yes | Search query to find documents |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0search-documentsScored across 1 tool
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.
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.
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.
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.
Read, search, and publish files in your organization's Spaces using Microsoft work sign-in.
Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.
Permissioned access to Outlook, OneDrive and Teams via the user's own Microsoft account
Securely search and manage workspace context files for AI agents and teams.