Skip to main content
Glama
shivankj11

slack-file-upload-mcp

by shivankj11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SLACK_TOKENNoGeneric fallback Slack token.
SLACK_BOT_TOKENNoFallback Slack bot token.
SLACK_MCP_TOKENNoThe Slack token. Falls back to SLACK_USER_TOKEN, SLACK_BOT_TOKEN, SLACK_TOKEN.
SLACK_USER_TOKENNoFallback Slack user token.
SLACK_FILE_UPLOAD_MAX_MBNoReject files larger than this before contacting Slack. Default: 1024.
SLACK_FILE_UPLOAD_ALLOWED_DIRSNoComma-separated directory prefixes the server may read from. Default: unset (any path).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
slack_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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.9/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools. Its purpose is singular and clearly described.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern with a server prefix: slack_upload_file. This is consistent and intuitive.

Tool Count4/5

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.

Completeness5/5

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

ActivityMaintained
ResponsivenessNo issues

Resources