Data as of: 20 November 2026
The short answer
All three vendors publish their own MCP server. Use it when you can.
- Notion: a hosted server from Notion, with OAuth sign-in. The simplest of the three to connect. It acts with everything your Notion account can access.
- Slack: a hosted server from Slack at
mcp.slack.com/mcp. It only works through a registered Slack app, and workspace admins approve it. - Google Drive: Google publishes remote MCP servers for Drive and other Workspace products. They are in the Google Workspace Developer Preview Program and need a Google Cloud project.
The official Slack and Google servers have setup requirements that an individual may not be able to meet. That is where community servers come in, and where you need to look hard at how they authenticate.
The official servers at a glance
| Notion | Slack | Google Drive | |
|---|---|---|---|
| Publisher | Notion | Slack | |
| Runs | Remote, at mcp.notion.com/mcp | Remote, at mcp.slack.com/mcp | Remote, at drivemcp.googleapis.com/mcp/v1 |
| Authentication | OAuth | OAuth, through a registered Slack app | OAuth, with your own OAuth client in a Google Cloud project |
| Who must approve | You | Your workspace admin | You, plus membership in the Developer Preview Program |
| Status | Available | Available to Slack Marketplace apps and internal apps | Developer preview |
| Listed in the SourceWeft directory | Yes | Not on 20 Nov 2026 | Not on 20 Nov 2026 |
Notion
Notion hosts its own MCP server at mcp.notion.com/mcp. You sign in with OAuth and pick a workspace. The connection then acts with your own Notion permissions: it can read and update whatever you can access in that workspace. It is not limited to pages you select.
Because the server needs sign-in, a directory cannot read its tool list in advance.
Notion also still serves a legacy SSE endpoint at mcp.notion.com/sse and says it will retire it on 23 February 2027. If a client is configured with that URL, switch it to the Streamable HTTP address above.
Some third-party gateways bundle Notion with other apps behind one login. They add a second company to the chain that sees your data, so prefer the official server unless you need the bundle.
Slack
Slack's own MCP server lets a client search channels, messages, files, and users, read channels and threads, send, schedule, and draft messages, add reactions, upload files, and work with canvases and lists.
Three requirements shape who can use it:
- It needs a registered Slack app. An MCP client must be backed by a Slack app with a fixed app ID. Slack uses that to let admins approve the client through the normal app approval process and to apply logging and rate limits.
- Only some apps qualify. Slack states that only apps published in the Slack Marketplace (its documentation also says "directory-published") and internal apps can use MCP. Unlisted apps cannot.
- It is remote only. The server speaks Streamable HTTP. Slack states that it does not support SSE connections or Dynamic Client Registration.
In practice: Slack says you can use the server through a partner-built client with no coding, and points to its Help Center for the current list of partner apps. If your AI application is not one of them, it needs its own Slack app in the Marketplace. If your company builds an internal app, your admin can enable it. If none of these is true, the official server is not available to you yet.
Community Slack servers
The SourceWeft directory lists community servers that reach Slack other ways. Authentication is what separates them.
| Server | Publisher | Runs | Authentication | Tools listed | License | Updated |
|---|---|---|---|---|---|---|
| Slack MCP Server | GitHub jtalk22 | Remote | OAuth | 20 | MIT | 3 Nov 2026 |
| Slack MCP Server | GitHub stevenvo | Local | Not declared in the listing | Not validated yet | MIT | 24 Oct 2026 |
| Slack MCP | GitHub mrfentmen | Local | Bot token, per its description | Not validated yet | Not declared | 26 Oct 2026 |
jtalk22/slack-mcp-server. Built for catching up: unreads, threads, and search. The directory lists its 20 tools, so you can read them before connecting. Its listing describes two ways to run it, a browser session or hosted OAuth. The table shows OAuth, which is what the directory records for the remote server. Check which mode you are setting up (see the note on session-token servers below).
stevenvo/slack-mcp-server. Reads conversations, threads, user profiles, and search results. Its description covers reading only.
mrfentmen/slack-mcp. Uses the Slack Web API with a bot token to list channels, read history, and post messages. A bot token comes from a Slack app that a workspace admin installs with defined scopes.
A note on session-token servers
Some community Slack servers authenticate with your personal browser session token instead of a Slack app. Their appeal is that they need no admin approval. That is also the problem: they act with everything your account can see, outside the approval and audit controls that Slack's own server is built around. In a work workspace, ask your admin and use an app-based route.
Google Drive
Google publishes remote MCP servers for Google Workspace. The products covered include Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, and Classroom. According to Google's setup guide, the servers inherit the same permissions and data governance controls as the user.
To use them you need:
- membership in the Google Workspace Developer Preview Program
- a Google Cloud project with the MCP service for each product enabled, such as the Google Drive MCP API
- an OAuth client ID configured for use by an AI agent
- an MCP client that can connect to remote servers over Streamable HTTP with your own OAuth client ID and secret. Google's guide has step-by-step instructions for Google Antigravity and for Claude on a paid plan, and generic settings for other clients
This is a developer setup, not a one-click connection. For a team with a Google Cloud project it is the right route. For an individual who wants an assistant to read a few Drive files, it is a lot. SourceWeft's own Google Drive connector is a different route: you pick the files to share, as described in Let an AI read only the files you pick: connect Google Drive or Dropbox to SourceWeft.
Community Google Drive servers
| Server | Publisher | Runs | Authentication | License | Version | Updated |
|---|---|---|---|---|---|---|
| Google Drive MCP | GitHub piotr-agier | Local | Your own Google OAuth credentials, set locally | MIT | 2.12.0 | 24 Oct 2026 |
| Google Drive MCP | renzojohnson.com | Local | Not declared in the listing | Not declared | 26.11.14 | 13 Nov 2026 |
| Google Drive | myagents.click | Remote | OAuth | Hosted service | 1.0.4 | 19 Nov 2026 |
piotr-agier/google-drive-mcp. A local server covering Drive, Docs, Sheets, Slides, and Calendar. You create your own Google OAuth credentials and it signs in locally. It is open source under MIT.
renzojohnson.com Google Drive MCP. A local server for searching files, organizing folders, and managing sharing. The listing declares no license.
myagents.click Google Drive. A remote server that creates and updates spreadsheets and documents in your Drive. It is a hosted third-party service, so your Drive access passes through that operator.
With a local server, the Google credentials stay on your machine. With a remote third-party server, the operator holds a token to your Drive. For most individuals the local option is the safer of the two.
Authentication at a glance
| Method | Who approves it | What the server can reach | Use it when |
|---|---|---|---|
| OAuth to the vendor's own server | You, and for Slack your admin | What you grant | Always preferred when available |
| Bot token from an app an admin installed | Your workspace admin | The scopes and channels the app was given | Team workspaces |
| Your own OAuth credentials, stored locally | You | What you grant, with credentials on your machine | Personal accounts and local servers |
| OAuth to a third-party hosted server | You | What you grant, held by the third party | Only when you trust the operator |
| Personal session token | Nobody | Everything your account can see | Avoid at work |
Before you connect a workspace tool
- Start read-only where the server or the scopes allow it.
- Share narrowly where you can. Give the connection specific folders or channels, not the whole workspace. Notion's server does not offer this: it acts with everything your account can access, so connect it with an account that sees only what the assistant should.
- Keep approval on for writes: posting messages, editing pages, changing sharing settings.
- Remember that content is untrusted. A document or message can contain text aimed at the model. An agent that reads a shared channel and can also post or share files is the combination to be careful with.
- Revoke when done. Remove the grant in Notion, Google, or Slack, not only in your AI app.
Browse more
The SourceWeft directory lists more options under Productivity & Workflow, Files & Storage, and Communication & Collaboration.
FAQ
Is there an official Notion MCP server? Yes. Notion publishes a hosted server under the notion.com namespace. It uses OAuth.
Is there an official Slack MCP server?
Yes, at mcp.slack.com/mcp. It works through a registered Slack app, and Slack limits it to apps published in the Slack Marketplace and internal apps. Workspace admins approve and manage the integration.
Is there an official Google Drive MCP server? Yes. Google publishes remote MCP servers for Workspace products, including Drive. They are part of the Google Workspace Developer Preview Program and need a Google Cloud project and an OAuth client.
Which Slack MCP server is safest for a company workspace? Slack's own, through an app your admin approves. If that is not available, use a server that authenticates through a Slack app with limited scopes. Avoid servers that use a personal session token.
Can an MCP server read all my Google Drive files? It can read what the granted scope allows. Choose the narrowest scope the server supports, and with community servers prefer a local one, where the credentials stay on your machine.
Do these servers work in a web-based AI app? The remote ones do. Local servers need a desktop host that can start a process on your machine.