Microsoft 365 File Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REGION | Yes | SEARCH REGION | |
| CLIENT_ID | Yes | MSGraph Client ID | |
| TENANT_ID | Yes | TENANT ID | |
| CLIENT_SECRET | Yes | MS Graph Client Secret |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_file_contentC | Get content of Microsoft 365 file by drive id and file id. |
| search_m365_filesC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
search_m365_files locates files via query and type, while get_file_content retrieves a specific file's content using drive and file IDs. One is discovery and the other is retrieval, so there is no overlap.
Both tool names follow a consistent verb_noun snake_case pattern: search + m365_files and get + file_content. This makes their purposes predictable and consistent.
Two tools is minimal, but it fits the server's search-focused purpose: discover files and fetch their content. It is slightly below the typical well-scoped range, but each tool earns its place.
The core workflow is covered: search returns resource identifiers that get_file_content can consume. There is no browse/list/metadata-only operation, but this is a minor gap for a search-oriented server.