Local MCP vs Ms 365 MCP Server
A side-by-side look at the Local MCP and Ms 365 MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Local MCP for communication work over a hosted endpoint; choose Ms 365 MCP Server for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Local MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose Ms 365 MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 57/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 67 | 1,048 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Local MCP | View Ms 365 MCP Server |
Tools & capabilities
Local MCP tools
No tool names declared yet. Check the project README from the listing page.
Ms 365 MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Local MCP
{
"mcpServers": {
"lanchuske-local-mcp": {
"url": "https://www.local-mcp.com/mcp"
}
}
}
Ms 365 MCP Server
{
"mcpServers": {
"softeria-ms-365-mcp-server": {
"command": "npx",
"args": [
"-y",
"@softeria/ms-365-mcp-server"
]
}
}
}
Frequently asked questions
Local MCP is categorized under Communication and uses a remote HTTP/SSE transport. Ms 365 MCP Server belongs to Communication and uses a local stdio subprocess. Pick Local MCP for communication work and Ms 365 MCP Server for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Local MCP is listed as free. Auth: no auth required. Ms 365 MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lanchuske-local-mcp and softeria-ms-365-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Local MCP has a quality signal of 57/100 (Good) with 4 views, 0 installs and 67 GitHub stars. Ms 365 MCP Server has 60/100 (Good) with 1 views, 0 installs and 1,048 GitHub stars.