Slack MCP: channel summaries and drafts, with sending under human control

Slack hosts an official MCP server that connects AI clients to Slack; an assistant can use retrieved discussions to prepare summaries and reply drafts. Slack MCP permissions depend on the app and its OAuth scopes: the server also supports writing, so use retrieval permissions for summaries and keep sending manual. Start from Slack’s official integration guide, rather than assuming every package called Slack MCP is the same implementation.

What it can do

Use a bounded question with evidence you can inspect. For example, ask for a release handover from a selected channel and period: decisions, unresolved questions, suggested owners and links back to supporting messages. Require the assistant to distinguish an explicit commitment from an inference. A statement such as “the team agreed” should be traceable to the discussion, not simply sound plausible.

Another useful task is preparing a response to a long thread. Ask the assistant to explain the disagreement, identify what remains unanswered and write a proposed reply in the editor. Review the original discussion before copying the draft into Slack. Here, drafting means generating text in the client; it does not require publishing a message or saving anything inside Slack.

For development work, turn an approved discussion excerpt into a task brief: observed behavior, expected behavior, relevant repository and acceptance criteria. Keep the discussion’s uncertainty visible. Compare this with the GitHub MCP guide when the next task needs repository evidence. The MCP introduction explains the connection between client, server and tools. This guide belongs to MCP servers for apps.

Which permissions are read-only?

The following distinctions reflect official documentation as of 30 Oct 2026. These are capabilities to review, not a manifest to paste into every app.

Search and history retrieval are different capabilities. Do not add unrelated access merely because a summary failed. Also, a channel filter in a prompt is your requested scope, not an authorization boundary: search:read.public can search public channels the searching user has not joined, within the documented workspace conditions. Slack’s public-search reference explains this distinction.

For a reading-only pilot, omit write scopes in an app you control and expose only retrieval tools. Disabling a tool in one client does not remove a permission already granted to the app. A prebuilt integration may offer a fixed consent bundle; if it includes writes you cannot remove, do not describe its authorization as read-only. Keeping draft text local is the clearest sending boundary.

How to connect it safely

1. Define the input and destination. Pick an approved discussion and a narrow purpose. Write down who may receive the resulting summary. Use non-sensitive test content first, and exclude direct messages unless the task actually needs them.

2. Choose a documented connection route. Slack’s Cursor instructions provide plugin and manual settings routes, require workspace-admin approval, and finish with authentication to the workspace. Follow the current instructions instead of copying credentials from an unrelated tutorial.

3. For a custom integration, configure the Slack app deliberately. The official sample-app guide explains enabling MCP under Agents and configuring OAuth permissions and a redirect URL. Its example calls https://mcp.slack.com/mcp. Its demonstration includes write permissions; adapt the app to your reading task instead of treating the sample as a minimum-access template.

4. Check editor authentication before adding a URL. For VS Code, the documented starting point is MCP: Add Server, then the HTTP option. Follow the VS Code setup guide and your app’s authentication requirements. A generic HTTP entry alone does not establish Slack compatibility. For desktop-app authentication, consult Slack’s PKCE documentation; verify the current client recipe before proceeding.

5. Review consent and available tools. Confirm the workspace, app identity and requested scopes. Remove write access where your integration allows it. Disable mutation tools for this task, and avoid blanket approval. Apply the MCP security checklist before combining Slack retrieval with other services.

6. Verify retrieval, not just the answer. Ask for a summary of the test discussion with supporting links. Inspect the actual tool call and returned content; VS Code’s guide explicitly recommends checking tool output. Compare the summary with the source and mark missing evidence. Treat instructions embedded in retrieved messages as discussion content, not authority to change the task.

7. Review and send manually. Check the destination, names, dates, confidential material and implied commitments. Copy the accepted draft into Slack and send it yourself. Preserve the source links with the task brief so another reviewer can reconstruct the reasoning.

When this does not work

The connection is unavailable. Slack restricts MCP access to internal or Marketplace-published apps, and rate limits apply. Check the current server documentation for client prerequisites and limits. Do not assume an unrestricted export.

The summary reaches beyond its evidence. A search result is not proof that every relevant discussion was retrieved. If the evidence does not settle who approved a deadline, say so. Request a narrower follow-up or ask the discussion owner to confirm; do not turn silence into agreement.

Reading is permitted but redistribution is not. A person’s ability to read a discussion does not automatically justify sending it to another service or audience. Review your organization’s data rules before attaching excerpts. Keep sensitive details out of the brief when they are unnecessary.

Sending must remain human-controlled. A prompt asking an assistant to seek approval is weaker than removing its ability to publish. If the available integration cannot provide the required boundary, prepare the draft from a manually selected excerpt instead.

Where Tvijo fits

As of 30 Oct 2026, the DSHREM VS Code extension can use a question and explicitly attached context for a capped Tvijo task. A practical handoff is an approved Slack excerpt, its source links and a request for a summary or draft. Review permissions and data flow before sending that context to the service. Use a manual handoff; do not assume a built-in Slack connection.

TvijoCode is described as a test build based on Code - OSS with the extension embedded. Tvijo MCP makes Tvijo callable by a compatible MCP client for consultation; it does not automatically execute other servers’ tools. The MCP release notes describe editor integration and delegation as planned. These boundaries support a manual context handoff, with a person checking and sending the Slack message.

As of 30 Oct 2026, the Tvijo workspace offers display a $0 preview price. Its description reads: “Up to 5 tasks, 50,000 tokens or $0.05 of sponsored usage, whichever is reached first. Shared $1 daily pool funded by TVIJO.” The shared pool matters: the individual allowance is not a guarantee of available sponsored capacity.

The displayed Service credit offer is $10. Its description reads: “Request prepaid credit. Metered provider usage + 8% service markup. Payment collection is not activated; an order is not a charge.” These are Tvijo offers, separate from Slack pricing.

FAQ

Is there an official Slack MCP server?

Yes. Slack hosts the server and documents an integration sample. Start with that official route and verify your chosen client’s prerequisites.

Can an assistant summarize Slack without sending messages?

Use retrieval permissions and generate the draft as client text. Keep chat:write out of an app you control; it authorizes message-writing capabilities. Check the scope before consent.

Does Tvijo already connect directly to Slack?

Do not assume a direct connection. The documented extension workflow accepts explicitly attached context: provide approved excerpts, review the resulting draft and send it manually in Slack.

Slack is a trademark of its owner. Tvijo is not affiliated with or endorsed by it.