組織の Sharepoint へのアクセスを提供するモデル コンテキスト プロトコル サーバー。
成分 | 手術 | リソース | 動的リソース | 道具 |
ユーザー | ❌ | ❌ | ❌ | |
ユーザーを読む | ❌ | ❌ | ❌ | |
ユーザーを探す | ❌ | ❌ | ❌ | |
サイト | ❌ | ❌ | ❌ | |
サイト一覧 | ✅ | ❌ | ❌ | |
サイトの詳細を取得 | ❌ | ❌ | ❌ | |
サブサイトの作成 | ❌ | ❌ | ❌ | |
サイトを削除 | ❌ | ❌ | ❌ | |
ドライブ | ❌ | ❌ | ❌ | |
フォルダの一覧 | ❌ | ❌ | ❌ | |
検索フォルダ | ❌ | ❌ | ✅ | |
フォルダを作成 | ❌ | ❌ | ❌ | |
フォルダを削除 | ❌ | ❌ | ❌ | |
ファイルをアップロード | ❌ | ❌ | ❌ | |
リスト項目 | ❌ | ✅ | ❌ | |
ファイルをダウンロード | ❌ | ❌ | ✅ | |
ファイルを読む | ✅ | ❌ | ❌ | |
ファイルを移動 | ❌ | ❌ | ❌ | |
ファイルをコピー | ❌ | ❌ | ❌ | |
リスト | ❌ | ❌ | ❌ | |
リストを作成 | ❌ | ❌ | ❌ | |
読むリスト | ❌ | ❌ | ❌ | |
リストに追加 | ❌ | ❌ | ❌ | |
更新リスト | ❌ | ❌ | ❌ | |
リストを削除 | ❌ | ❌ | ❌ | |
カレンダー | ❌ | ❌ | ❌ | |
イベントを作成 | ❌ | ❌ | ❌ | |
イベントを読む | ❌ | ❌ | ❌ | |
更新イベント | ❌ | ❌ | ❌ | |
イベントを削除 | ❌ | ❌ | ❌ |
文書概要
関連文書を見つける
フォルダを探索する
Related MCP server: SharePoint MCP Server
.env.example を .env としてコピーします。
必須項目を入力してください
ルートから
npx @modelcontextprotocol/inspector -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 -- node dist/index.jsこのサーバーを 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
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.
Provides metadata information to AI agents through the search API.