slack-file-upload-mcp
Allows uploading local files to Slack channels, DMs, or thread replies with an optional message, title, and filename override.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@slack-file-upload-mcp upload ~/Downloads/report.csv to #general with message 'Q3 numbers attached'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
slack-file-upload-mcp
A one-tool MCP server that does the thing the normal Slack MCP can't: post a local file to Slack, with a message.
The Slack MCP sends text (slack_send_message) and reads files, but has no way to put a file from your disk into a channel. Run this alongside it and an agent can share a screenshot, CSV, log, or PDF directly.
The tool
slack_upload_file
Arg | Required | Meaning |
| ✅ | Absolute local path ( |
| ✅ | Channel id ( |
| Text posted with the file (Slack's | |
| File title in Slack. Defaults to the filename. | |
| Override the stored name. Defaults to the local basename. | |
| Post as a reply in this thread instead of the channel root. |
Returns one line: Uploaded report.csv (4821 bytes) to C09ABCD1234 · file_id=F0… · ts=1756… · https://…. The ts is the share timestamp, so the Slack MCP can thread replies under the uploaded file.
Uploads go through Slack's current files.getUploadURLExternal → upload → files.completeUploadExternal flow (via slack_sdk's files_upload_v2); the retired files.upload endpoint is not used.
Related MCP server: Slack MCP Server
Setup
Token. A user token (
xoxp-…) or bot token (xoxb-…) with:files:write— required.channels:read+groups:read— only needed to resolve#name→ id. Passing aC…id works without them.im:write— only needed to DM aU…user id.
A bot token must be invited to the channel (
/invite @yourapp); a user token posts as you.manifest.yamlin this repo creates an app with exactly those scopes: api.slack.com/apps → Create New App → From a manifest → pick the workspace → paste the file → Create → Install to Workspace (admin approval may be required) → OAuth & Permissions → copy the User OAuth Token (xoxp-…).It's deliberately a separate app from any existing one: adding a scope to an installed app forces a reinstall, which rotates that app's token and breaks whatever else was using it.
Register the server (token lives in the MCP env, not in the repo):
claude mcp add slack-file-upload --scope user \ --env SLACK_MCP_TOKEN=xoxp-your-token \ -- uv run --directory /path/to/slack-file-upload-mcp slack-file-upload-mcp serveVerify:
SLACK_MCP_TOKEN=… uv run slack-file-upload-mcp whoami
Configuration
Env var | Default | Purpose |
| — | The token. Falls back to |
| unset (any path) | Comma-separated directory prefixes the server may read from. Set it to confine a prompt-injected agent to e.g. |
|
| Reject files larger than this before contacting Slack. Slack's own ceiling is 1 GB. |
Guardrails
Path must be absolute and resolve to an existing regular file; directories and symlink targets outside
SLACK_FILE_UPLOAD_ALLOWED_DIRSare rejected (the path isresolve()d before the allowlist check).Empty files are rejected up front — Slack's upload-URL endpoint requires a non-zero length and fails opaquely on 0 bytes.
Slack API errors are translated into actionable text (
not_in_channel→ "invite the app to the channel",missing_scope→ which scopes).
CLI
uv run slack-file-upload-mcp serve # stdio MCP (also the bare default)
uv run slack-file-upload-mcp whoami # verify the token
uv run slack-file-upload-mcp upload ~/x.png '#general' -m 'here you go'upload runs the exact code path the MCP tool runs — useful for smoke tests without a client.
Tests
uv run pytest # offline; the Slack client is stubbedAvailable Tools
1 toolslack_upload_fileA
Upload a local file to a Slack channel, DM, or thread, with an optional message.
This is the piece the Slack MCP is missing: it posts files, not just text. Use it whenever the thing to share lives on disk (a screenshot, CSV, log, PDF) instead of pasting the contents into a message.
Args:
file_path: Absolute path to the local file (~ is expanded). Must be a
regular, non-empty file.
channel: Channel id (C…/G…), DM id (D…), #channel-name, or a
user id (U…) to upload into a DM with that person. Prefer the id:
resolving a name costs an extra API call and needs channels:read, so a
token without it fails with missing_scope — retry with the id, which
the Slack MCP's own results already carry.
message: Text posted with the file (Slack's initial_comment). Supports
Slack mrkdwn — *bold*, _italic_, <url|label>.
title: File title shown in Slack. Defaults to the filename.
filename: Override the name Slack stores. Defaults to the local basename.
thread_ts: Post the file as a reply in this thread instead of the channel root.
Returns: A one-line confirmation with the file id and permalink.
Inputs: channel (required), file_path (required), title, message, +2 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion with other tools. Its purpose is singular and clearly described.
The single tool name follows a clear verb_noun pattern with a server prefix: slack_upload_file. This is consistent and intuitive.
The server is intentionally scoped to a single file-upload operation, so one tool is reasonable. It is slightly under the typical 3-15 range but not excessive or sparse given the narrow purpose.
The tool covers the core upload workflow with support for file path, channel, message, title, filename, and thread replies. No obvious missing operations are needed for the stated file-upload focus.
Maintenance
Related MCP Connectors
Enable interaction with Slack workspaces. Supports subscribing to Slack events through Resources.
File uploads for AI agents. Upload, list, and manage files. No signup required.
File tools for your AI chat: PDF tables to Excel, merge PDFs, images to PDF, fill PDF forms.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with Slack workspaces through comprehensive channel management, messaging, user management, file uploads, and Block Kit formatting. Features secure credential storage via macOS Keychain and supports all major Slack operations including reactions and workspace information.263MIT
- AlicenseAqualityDmaintenanceEnables comprehensive Slack workspace integration through AI assistants, allowing users to manage channels, send messages, upload files, search conversations, and interact with users through natural language commands.17ISC
- AlicenseNot gradedqualityDmaintenanceEnables secure downloading and access to Slack files and images using authenticated Bot User OAuth tokens. Integrates with Claude Code Action to allow Claude to analyze screenshots and files shared in Slack channels.1MIT
- FlicenseAqualityNot gradedmaintenanceEnables two-way communication between Claude and Slack for posting messages, managing threads, and handling files. It specifically supports asynchronous workflows by allowing Claude to poll for remote user replies and send task notifications.9-