com.mcparmory/slack
PYPI · MCPARMORY-SLACK · 2 COMPONENTS · SCANNED SEP 20
Manage channels, conversations, users, and workspace apps programmatically
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 7167 tokens (~99/item across 72 items; 72 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety95
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 11 of 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_me_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 72 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/slack MCP server?
com.mcparmory/slack runs locally as a PyPI package, launched with uvx mcparmory-slack. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-slack
claude mcp add com-mcparmory-slack -- uvx mcparmory-slack
{
"mcpServers": {
"com-mcparmory-slack": {
"command": "uvx",
"args": [
"mcparmory-slack"
]
}
}
} {
"servers": {
"com-mcparmory-slack": {
"command": "uvx",
"args": [
"mcparmory-slack"
]
}
}
} codex mcp add com-mcparmory-slack -- uvx mcparmory-slack
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-slack": {
"type": "local",
"command": [
"uvx",
"mcparmory-slack"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-slack --command uvx --arg mcparmory-slack
mcp_servers:
com-mcparmory-slack:
command: "uvx"
args: ["mcparmory-slack"] {
"McpServers": {
"com-mcparmory-slack": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-slack"
]
}
}
} assistant mcp add com-mcparmory-slack -t stdio -c uvx -a mcparmory-slack
{
"mcpServers": {
"com-mcparmory-slack": {
"command": "uvx",
"args": [
"mcparmory-slack"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcparmory-slack@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_pin_to_channel Add Pin to Channel ~83
Pins a message to a channel, making it easily accessible to channel members. Requires authentication with pins:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | The channel where the item will be pinned. Specify the channel ID or name. |
| timestamp | string | – | The timestamp of the message to pin. Use the message's timestamp identifier to specify which message should be pinned. |
No output schema declared.
No examples provided.
add_reaction_to_message Add Reaction to Message ~110
Adds an emoji reaction to a message in a channel. Requires authentication with reactions:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | The channel ID where the message to react to is located. |
| name | string | yes | The emoji name to add as a reaction (e.g., 'thumbsup', 'heart'). Use the emoji name without colons or special characters. |
| timestamp | string | yes | The message timestamp (in seconds or milliseconds since epoch) identifying which message to add the reaction to. |
No output schema declared.
No examples provided.
add_star Add Star ~111
Adds a star to a specific item, such as a file comment or message. Requires authentication with stars:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel to add star to, or channel where the message to add star to was posted (used with `timestamp`). |
| file_comment | string | – | The file comment identifier to star. Specify either this or timestamp, but not both. |
| timestamp | string | – | The timestamp of the message to star. Specify either this or file_comment, but not both. |
No output schema declared.
No examples provided.
add_users_to_conversation Add Users to Conversation ~86
Adds one or more users to a conversation channel. Specify users by their IDs in a comma-separated list.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | The ID of the public or private channel to invite user(s) to. |
| users | string | – | A comma-separated list of user IDs to invite to the conversation. Up to 1000 users can be added in a single request. |
No output schema declared.
No examples provided.
archive_conversation Archive Conversation ~40
Archives a conversation, removing it from the active conversation list while preserving its history for future reference.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | ID of conversation to archive |
No output schema declared.
No examples provided.
close_conversation Close Conversation ~49
Closes an active direct message conversation, either between two users or among multiple participants. This action archives the conversation and prevents further messages in that thread.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Conversation to close. |
No output schema declared.
No examples provided.
create_conversation Create Conversation ~90
Creates a new conversation channel that can be either public or private. Public channels are visible to all users, while private channels restrict access to invited members only.
| Name | Type | Req | Description |
|---|---|---|---|
| is_private | boolean | – | Set to true to create a private channel with restricted access, or false (default) to create a public channel visible to all users. |
| name | string | – | Name of the public or private channel to create |
No output schema declared.
No examples provided.
create_reminder Create Reminder ~144
Creates a reminder that will be delivered at a specified time. The reminder can be scheduled for a specific Unix timestamp, a relative time within 24 hours, or using natural language descriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The reminder message content that will be displayed to the recipient. |
| time | string | yes | When the reminder should trigger: a Unix timestamp (up to five years in the future), seconds from now (for reminders within 24 hours), or natural language phrasing like 'in 15 minutes' or 'every Thur… |
| user | string | – | The user who will receive the reminder. If omitted, the reminder is assigned to the user who created it. |
No output schema declared.
No examples provided.
create_usergroup Create User Group ~150
Create a new User Group with a unique name and optional configuration for channels, description, and mention handle.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | string | – | Comma-separated list of encoded channel IDs to set as defaults for this User Group. |
| description | string | – | A brief description of the User Group's purpose or membership. |
| handle | string | – | A unique mention handle for the User Group. Must not conflict with existing channel names, user handles, or other User Group handles. |
| include_count | boolean | – | When enabled, the response will include the count of users currently in the User Group. |
| name | string | yes | A unique name for the User Group. Must not duplicate any existing User Group names. |
No output schema declared.
No examples provided.
delete_file Delete File ~35
Permanently deletes a file from the system. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | ID of file to delete. |
No output schema declared.
No examples provided.
delete_file_comment Delete File Comment ~56
Deletes an existing comment on a file. Requires the comment ID to identify which comment to remove.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | File to delete a comment from. |
| id | string | – | The unique identifier of the comment to delete. |
No output schema declared.
No examples provided.
delete_message Delete Message ~137
Deletes a message from a channel. The message is identified by its timestamp, and deletion can be performed either as the authenticated user or as a bot, depending on the scope and parameters provided.
| Name | Type | Req | Description |
|---|---|---|---|
| as_user | boolean | – | When true, deletes the message as the authenticated user using the `chat:write:user` scope (applies to bot users as well). When false or omitted, deletes the message using the `chat:write:bot` scope. |
| channel | string | – | Channel containing the message to be deleted. |
| ts | number | – | The timestamp of the message to delete. This uniquely identifies the message within its channel. |
No output schema declared.
No examples provided.
delete_scheduled_message Delete Scheduled Message ~122
Removes a pending scheduled message from the queue before it is posted to a channel.
| Name | Type | Req | Description |
|---|---|---|---|
| as_user | boolean | – | When true, deletes the message as the authenticated user with `chat:write:user` scope (applies to bot users as well). When false or omitted, uses `chat:write:bot` scope instead. |
| channel | string | yes | The channel ID where the scheduled message is queued to be posted. |
| scheduled_message_id | string | yes | The unique identifier of the scheduled message to delete, as returned from the chat.scheduleMessage operation. |
No output schema declared.
No examples provided.
delete_user_photo Delete User Photo ~24
Remove the user's profile photo. Requires authentication with users.profile:write scope.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
disable_dnd Disable Do Not Disturb ~27
Immediately deactivates the current user's Do Not Disturb mode, restoring normal notification delivery.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
disable_usergroup Disable Usergroup ~75
Disable an existing User Group, preventing its use while preserving its configuration and membership data.
| Name | Type | Req | Description |
|---|---|---|---|
| include_count | boolean | – | When enabled, the response will include a count of users currently in the User Group. |
| usergroup | string | yes | The encoded ID of the User Group to disable. This identifier uniquely identifies the target group. |
No output schema declared.
No examples provided.
enable_do_not_disturb Enable Do Not Disturb ~74
Activates Do Not Disturb mode for the current user with a specified duration. If Do Not Disturb is already active, this updates the snooze duration.
| Name | Type | Req | Description |
|---|---|---|---|
| num_minutes | string | yes | Duration in minutes from the current time until Do Not Disturb mode should automatically turn off. Must be a positive integer. |
No output schema declared.
No examples provided.
enable_file_public_sharing Enable File Public Sharing ~45
Enables public sharing for a file by generating a shareable public URL that allows external users to access the file without authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | File to share |
No output schema declared.
No examples provided.
enable_usergroup Enable Usergroup ~79
Activate a disabled User Group, making it available for use. Optionally retrieve the current member count.
| Name | Type | Req | Description |
|---|---|---|---|
| include_count | boolean | – | When true, the response includes the total number of users currently in the User Group. |
| usergroup | string | yes | The encoded ID of the User Group to enable. This identifier uniquely identifies the target User Group. |
No output schema declared.
No examples provided.
end_dnd_snooze End DND Snooze ~30
Immediately ends the current user's do-not-disturb snooze mode, restoring normal notification delivery.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_bot_info Get Bot Info ~55
Retrieves detailed information about a specific bot user. Requires authentication with users:read scope.
| Name | Type | Req | Description |
|---|---|---|---|
| bot | string | – | The bot user identifier to retrieve information for. If not provided, returns information about the authenticated bot making the request. |
No output schema declared.
No examples provided.
get_conversation_history Get Conversation History ~172
Retrieves the message and event history for a conversation within an optional time range. Results can be paginated and filtered by timestamp boundaries.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Conversation ID to fetch history for. |
| inclusive | boolean | – | When true, includes messages with timestamps exactly matching the latest or oldest values; when false, excludes them. Only applies when at least one timestamp boundary is specified. |
| latest | number | – | Unix timestamp marking the end of the time range; only messages up to this point are included in results. |
| limit | integer | – | Maximum number of messages to return per request. The actual number returned may be less than requested, even if additional messages exist. |
| oldest | number | – | Unix timestamp marking the start of the time range; only messages from this point forward are included in results. |
No output schema declared.
No examples provided.
get_conversation_info Get Conversation Info ~81
Retrieve detailed information about a specific conversation, optionally including locale and member count metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Conversation ID to learn more about |
| include_locale | boolean | – | Include the locale language and region information for the conversation in the response. |
| include_num_members | boolean | – | Include the total number of members in the conversation in the response. |
No output schema declared.
No examples provided.
get_conversation_thread Get Conversation Thread ~227
Retrieve a thread of messages from a conversation, including a parent message and all its replies within an optional time range.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Conversation ID to fetch thread from. |
| inclusive | boolean | – | When true, includes messages that match the exact latest or oldest timestamp in results. Only applies when at least one of those timestamps is specified. |
| latest | number | – | The end of the time range for filtering messages, specified as a Unix timestamp. Only messages up to this time will be included in results. |
| limit | integer | – | The maximum number of messages to return in a single response. The actual number returned may be less if the thread contains fewer messages than requested. |
| oldest | number | – | The start of the time range for filtering messages, specified as a Unix timestamp. Only messages from this time onward will be included in results. |
| ts | number | – | The timestamp of the parent message whose thread you want to retrieve. This message must exist and can have zero or more replies; if there are no replies, only the parent message itself is returned. |
No output schema declared.
No examples provided.
get_dnd_status Get Do Not Disturb Status ~67
Retrieves the current Do Not Disturb status for a user, indicating whether they have notifications muted or disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| user | string | – | The user ID or username to fetch the Do Not Disturb status for. If not provided, returns the status for the authenticated user making the request. |
No output schema declared.
No examples provided.
get_file_info Get File Info ~82
Retrieves metadata and information about a specific file, including details such as size, type, timestamps, and other file attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Specify a file by providing its ID. |
| limit | integer | – | The maximum number of file records to return in the response. The API may return fewer items than requested if the end of the list is reached. |
No output schema declared.
No examples provided.
get_message_permalink Get Message Permalink ~89
Generate a shareable permalink URL for a specific message in a channel or conversation. This allows you to create direct links to individual messages that persist even if the original message is edited.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | The unique identifier of the channel or conversation containing the target message. |
| message_ts | string | yes | The timestamp value (`ts`) of the message, which uniquely identifies it within the channel. |
No output schema declared.
No examples provided.
get_reactions Get Reactions ~167
Retrieves all reactions added to a specific message, file comment, or other item. Use this to see what emoji reactions users have added to content.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel where the message to get reactions for was posted. |
| file | string | – | File to get reactions for. |
| file_comment | string | – | The file comment to retrieve reactions for. Specify either this parameter, timestamp, or neither to get reactions for the item context. |
| full | boolean | – | When true, returns the complete list of all reactions. When false or omitted, may return a truncated list. |
| timestamp | string | – | The timestamp of the message to retrieve reactions for, typically in Unix epoch format. Specify either this parameter, file_comment, or neither to get reactions for the item context. |
No output schema declared.
No examples provided.
get_team_dnd_status Get Team Do Not Disturb Status ~68
Retrieves the Do Not Disturb status for specified users on a team, allowing you to check up to 50 users at once.
| Name | Type | Req | Description |
|---|---|---|---|
| users | string | yes | Comma-separated list of user identifiers to retrieve Do Not Disturb status for. Supports up to 50 users per request. |
No output schema declared.
No examples provided.
get_team_info Get Team Info ~81
Retrieves information about a team. If no team is specified, returns information about the authenticated user's current team. The authenticated token must have the `team:read` scope.
| Name | Type | Req | Description |
|---|---|---|---|
| team | string | – | Optional team identifier to retrieve information for a specific team. If omitted, returns the current team. Only returns teams accessible to the authenticated token through external shared channels. |
No output schema declared.
No examples provided.
get_team_profile Get Team Profile ~43
Retrieve detailed profile information for a team, with optional filtering by visibility settings.
| Name | Type | Req | Description |
|---|---|---|---|
| visibility | string | – | Optional filter to retrieve only team profiles matching a specific visibility level. |
No output schema declared.
No examples provided.
get_user_by_email Get User by Email ~59
Retrieve a user account by their email address. Returns the user object if found in the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address of the user to look up. Must be a valid email address associated with a user in the workspace. |
No output schema declared.
No examples provided.
get_user_info Get User Info ~76
Retrieves detailed information about a specific user, optionally including their locale preference.
| Name | Type | Req | Description |
|---|---|---|---|
| include_locale | boolean | – | Set to `true` to include the user's locale in the response; defaults to `false` if omitted. |
| user | string | – | The user identifier to retrieve information for. If omitted, returns information for the authenticated user. |
No output schema declared.
No examples provided.
get_user_presence Get User Presence ~59
Retrieves the presence status of a user. If no user is specified, returns the presence information for the authenticated user.
| Name | Type | Req | Description |
|---|---|---|---|
| user | string | – | The user whose presence information should be retrieved. If omitted, defaults to the authenticated user making the request. |
No output schema declared.
No examples provided.
get_user_profile Get User Profile ~89
Retrieves detailed profile information for a specified user or the authenticated user. Requires authentication with users.profile:read scope.
| Name | Type | Req | Description |
|---|---|---|---|
| include_labels | boolean | – | When enabled, includes human-readable labels for each identifier in custom profile fields, making the response more interpretable. |
| user | string | – | The user identifier to retrieve profile information for. If omitted, returns the profile of the authenticated user making the request. |
No output schema declared.
No examples provided.
join_conversation Join Conversation ~41
Joins the authenticated user to an existing conversation, enabling participation in the conversation's messages and interactions.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | ID of conversation to join |
No output schema declared.
No examples provided.
leave_conversation Leave Conversation ~36
Removes the authenticated user from a conversation, ending their participation and access to that conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Conversation to leave |
No output schema declared.
No examples provided.
list_channel_pins List Channel Pins ~54
Retrieves all items pinned to a specified channel. Pinned items are messages or files that have been marked for easy reference within the channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | The channel ID or name to retrieve pinned items from. |
No output schema declared.
No examples provided.
list_conversation_members List Conversation Members ~84
Retrieve a paginated list of members in a conversation. Use the limit parameter to control the number of results returned per request.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | ID of the conversation to retrieve members for |
| limit | integer | – | Maximum number of members to return in a single request. The API may return fewer members than requested if the end of the list is reached. |
No output schema declared.
No examples provided.
list_conversations List Conversations ~147
Retrieves a list of all conversations (channels and direct messages) in a Slack workspace, with options to filter by type and archive status.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_archived | boolean | – | When set to true, archived channels are excluded from the results. Useful for focusing on active conversations only. |
| limit | integer | – | Maximum number of conversations to return per request, up to 1000. The API may return fewer items than requested even if more results are available. |
| types | string | – | Filters conversations by type using a comma-separated list. Supported types are public_channel, private_channel, mpim (multi-person direct messages), and im (direct messages). Omit to include all typ… |
No output schema declared.
No examples provided.
list_emoji List Emoji ~36
Retrieves all custom emoji configured for the workspace. This includes emoji names, URLs, and metadata for all custom emoji available to team members.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_files List Files ~184
Retrieve a list of files with optional filtering by user, date range, file type, and visibility. Supports showing truncated information for files hidden due to age or team file limits.
| Name | Type | Req | Description |
|---|---|---|---|
| show_files_hidden_by_limit | boolean | – | When enabled, includes truncated file information for files hidden due to age or the team exceeding file storage limits. Defaults to false. |
| ts_from | number | – | Filter results to files created on or after this timestamp (inclusive). Use Unix timestamp format. |
| ts_to | number | – | Filter results to files created on or before this timestamp (inclusive). Use Unix timestamp format. |
| types | string | – | Filter results by file type. Accepts multiple comma-separated values (e.g., spaces,snippets). Defaults to all types if not specified. |
| user | string | – | Filter results to files created by a specific user. Provide the user identifier. |
No output schema declared.
No examples provided.
list_scheduled_messages List Scheduled Messages ~126
Retrieves a list of scheduled messages, optionally filtered by a time range. Use the oldest and latest parameters to narrow results to a specific period.
| Name | Type | Req | Description |
|---|---|---|---|
| latest | number | – | A UNIX timestamp marking the most recent message to include in the results. Messages scheduled at or before this time will be returned. |
| limit | integer | – | The maximum number of scheduled messages to return in a single response. Useful for pagination and controlling response size. |
| oldest | number | – | A UNIX timestamp marking the oldest message to include in the results. Messages scheduled at or after this time will be returned. |
No output schema declared.
No examples provided.
list_stars List Stars ~56
Retrieves a list of stars for the authenticated user, with optional pagination control.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of items to return per request. The API may return fewer items than requested if the end of the list is reached. |
No output schema declared.
No examples provided.
list_user_conversations List User Conversations ~176
Retrieve a list of conversations (channels and direct messages) that the calling user has access to, with optional filtering by user membership, conversation type, and archive status.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_archived | boolean | – | Set to true to exclude archived conversations from the results. |
| limit | integer | – | Maximum number of conversations to return per request. Must be between 1 and 1000; the API may return fewer items than requested even if more results are available. |
| types | string | – | Filter by conversation type using a comma-separated list. Supported types are: public_channel, private_channel, mpim (multi-person direct message), and im (direct message). |
| user | string | – | Filter conversations to only those where a specific user is a member. Non-public channels are only included if the calling user shares membership in them. |
No output schema declared.
No examples provided.
list_user_reactions List User Reactions ~115
Retrieves a list of emoji reactions made by a user. By default, returns reactions from the authenticated user, but can be filtered to show reactions from a specific user.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | When enabled, returns the complete list of all reactions without pagination limits. |
| limit | integer | – | Maximum number of reactions to return per request. The actual number returned may be less than requested if fewer items remain. |
| user | string | – | The user whose reactions to retrieve. If not specified, defaults to the authenticated user. |
No output schema declared.
No examples provided.
list_usergroup_members List Usergroup Members ~85
Retrieve all users who are members of a specified User Group. Optionally include users from disabled User Groups in the results.
| Name | Type | Req | Description |
|---|---|---|---|
| include_disabled | boolean | – | When enabled, includes results from User Groups that are currently disabled. By default, only active User Groups are included. |
| usergroup | string | yes | The encoded ID of the User Group whose members you want to list. |
No output schema declared.
No examples provided.
list_usergroups List User Groups ~91
Retrieve all User Groups configured for a team, with optional details about group membership and status.
| Name | Type | Req | Description |
|---|---|---|---|
| include_count | boolean | – | Include the total count of users in each User Group without listing individual members. |
| include_disabled | boolean | – | Include User Groups that have been disabled in addition to active groups. |
| include_users | boolean | – | Include the complete list of users belonging to each User Group in the response. |
No output schema declared.
No examples provided.
list_users List Users ~111
Retrieves all users in a Slack workspace. Results can be paginated and optionally include user locale information.
| Name | Type | Req | Description |
|---|---|---|---|
| include_locale | boolean | – | Include the locale setting for each user in the response. Defaults to false; set to true only if locale information is needed, as it may increase response size. |
| limit | integer | – | Maximum number of users to return per request. Omitting this parameter attempts to return the entire user list, which may fail if the workspace is large; include a limit to ensure reliable pagination. |
No output schema declared.
No examples provided.
mark_conversation_read Mark Conversation Read ~91
Mark a conversation as read by setting the read cursor to a specific message timestamp. This updates your read position in the channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel or conversation to set the read cursor for. |
| ts | number | yes | The message timestamp to mark as read. If provided, sets your read cursor to this message; if omitted, marks the entire conversation as read up to the current time. |
No output schema declared.
No examples provided.
What is the com.mcparmory/slack MCP server?
com.mcparmory/slack is an MCP server listed in the public MCP registry as com.mcparmory/slack. Manage channels, conversations, users, and workspace apps programmatically. This page covers its PyPI package (mcparmory-slack).
Is the com.mcparmory/slack MCP server safe to use?
com.mcparmory/slack scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/slack MCP server expose?
com.mcparmory/slack exposes 72 tools: verify_authentication, get_bot_info, update_call, delete_message, delete_scheduled_message, and 67 more. Their descriptions and schemas cost roughly 7,167 tokens of context every time the server is loaded.
Is the com.mcparmory/slack MCP server still maintained?
com.mcparmory/slack is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.