181c4f6ff5
The ms365 / microsoft-365 entries ship M365 as a manual type:http MCP server. That auth path cannot succeed: the M365 server's OAuth client registration only permits the claude.ai callback, so any client-initiated OAuth flow (localhost or claude:// redirect) is rejected by the identity provider before the consent screen ever shows (AADSTS50011). Users connect Microsoft 365 through the claude.ai Connectors directory instead, which uses the registered callback and works. Plugin skills reference tools via ~~category placeholders (see CONNECTORS.md), not the ms365 server key, so no content changes are needed. Bumps each touched plugin's version so the update distributes to existing installs. Co-authored-by: Claude <noreply@anthropic.com>
29 lines
529 B
JSON
29 lines
529 B
JSON
{
|
|
"mcpServers": {
|
|
"slack": {
|
|
"type": "http",
|
|
"url": "https://mcp.slack.com/mcp",
|
|
"oauth": {
|
|
"clientId": "1601185624273.8899143856786",
|
|
"callbackPort": 3118
|
|
}
|
|
},
|
|
"google calendar": {
|
|
"type": "http",
|
|
"url": ""
|
|
},
|
|
"gmail": {
|
|
"type": "http",
|
|
"url": ""
|
|
},
|
|
"notion": {
|
|
"type": "http",
|
|
"url": "https://mcp.notion.com/mcp"
|
|
},
|
|
"atlassian": {
|
|
"type": "http",
|
|
"url": "https://mcp.atlassian.com/v1/mcp"
|
|
}
|
|
}
|
|
}
|