Document the Slack MCP integration - #73
Open
playerzero-ai[bot] wants to merge 1 commit into
Open
Conversation
Connecting Slack now gives PlayerZero a set of Slack tools it can use during a Player thread or a workflow run, and organization owners can choose which of those tools it may call. The public docs said nothing about any of it. Adds connector/slack-mcp.mdx as the substantive page: what the tools cover, how to turn individual tools off and what happens when PlayerZero calls one that is off, which project work can reach the connection, and how the approval gate applies when PlayerZero posts, revises, or deletes a message. Extends connector/slack.mdx with a Slack Tools for PlayerZero section and a Reconnecting an Existing Connection subsection, since an organization that connected Slack before this release has to disable and re-enable to pick the tools up, and both steps now require an organization owner. Distinguishes the PlayerZero-managed Slack connection from a self-registered server on connector/remote-mcp-servers.mdx, and names Slack tool policy as an owner-only action in the general settings and membership guide. Adds the August 2026 changelog page with one entry, and registers both new pages in docs.json. Notes for review: - The tool names and their descriptions come from the live Slack MCP settings page. The implementations are not in this repo or in portal, so anyone with access to them is worth a second pair of eyes on two claims: that editing and deleting apply only to messages PlayerZero posted, and that search reaches only channels the bot belongs to. - The page deliberately does not deny capabilities that the Slack scopes table implies, such as file sharing. It describes what the tool list covers and leaves it there. - No screenshots. Every other connector page is text-only, and the one capture available names a real person and real repositories, so it needs a re-shoot on a demo organization first. - The changelog entry is here rather than on its own branch. Say the word and it can be split out to be merged independently, as the July changelog was. Reference: https://playerzero.ai/pz/pzdocs/channel/6a7233df1c33e9176bafa039/player/6a7372e99617530a9be52676 Co-authored-by: PlayerZero <player@playerzero.ai>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Connecting Slack now gives PlayerZero a set of Slack tools it can use
during a Player thread or a workflow run, and organization owners can
choose which of those tools it may call. The public docs said nothing
about any of it.
Adds connector/slack-mcp.mdx as the substantive page: what the tools
cover, how to turn individual tools off and what happens when PlayerZero
calls one that is off, which project work can reach the connection, and
how the approval gate applies when PlayerZero posts, revises, or deletes
a message.
Extends connector/slack.mdx with a Slack Tools for PlayerZero section
and a Reconnecting an Existing Connection subsection, since an
organization that connected Slack before this release has to disable and
re-enable to pick the tools up, and both steps now require an
organization owner. Distinguishes the PlayerZero-managed Slack
connection from a self-registered server on
connector/remote-mcp-servers.mdx, and names Slack tool policy as an
owner-only action in the general settings and membership guide.
Adds the August 2026 changelog page with one entry, and registers both
new pages in docs.json.
Notes for review:
settings page. The implementations are not in this repo or in portal,
so anyone with access to them is worth a second pair of eyes on two
claims: that editing and deleting apply only to messages PlayerZero
posted, and that search reaches only channels the bot belongs to.
scopes table implies, such as file sharing. It describes what the tool
list covers and leaves it there.
capture available names a real person and real repositories, so it
needs a re-shoot on a demo organization first.
word and it can be split out to be merged independently, as the July
changelog was.
Reference:
https://playerzero.ai/pz/pzdocs/channel/6a7233df1c33e9176bafa039/player/6a7372e99617530a9be52676