docs(slack): cover both Slack MCP and Slack API with in-page tabs#411
Draft
leet-c1 wants to merge 2 commits into
Draft
docs(slack): cover both Slack MCP and Slack API with in-page tabs#411leet-c1 wants to merge 2 commits into
leet-c1 wants to merge 2 commits into
Conversation
Restructure the Slack MCP server page to cover both catalog connectors: Slack (MCP), Slack's own search/read/message tools, leads as the recommended option; Slack (API), the REST-based connector, follows as a secondary section. Both use per-user OAuth with a customer-created Slack app (no Dynamic Client Registration) and user token scopes only. Add a copy/paste Slack app manifest to each connector's setup steps so admins can use Slack's "Create New App > From a manifest" flow instead of clicking through the scope picker, with default (read-only) scopes and commented-out optional (write) scopes to uncomment as needed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adopt a comparison table plus a Tabs layout (Slack MCP first/default, Slack API second), matching the approved Notion MCP/API precedent. Each tab holds that connector's full per-user OAuth setup with the copy/paste Slack app manifest tucked into an Accordion; shared closing sections (credential sharing, tool discovery/governance, rotation) follow. Correct the auth story: Slack MCP supports per-user OAuth (recommended) or a shared static Slack user token; Slack API supports per-user OAuth only. Neither uses dynamic client registration, so a Slack app with a client ID and secret is always required. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Reworks the Slack MCP server setup page to cover both Slack connectors and lead with the hosted MCP option:
The two are easy to confuse in the catalog, so the page opens with a comparison table (who hosts the server, authentication, access scoping, tool surface, setup effort) and a recommendation, then splits the setup into in-page tabs.
What changed
<Tabs>: Slack (MCP) (default) and Slack (API), each with its own "create the Slack app → scopes → register" flow.<Accordion>blocks so they don't clutter the page — an admin can use Slack's Create New App → From a manifest flow instead of adding scopes by hand.Follows the tabbed pattern introduced in #397 (Notion MCP vs Notion API).
Test plan
npx mint broken-linkspasses for this page (site-wide crawl completes; no broken links attributable toslack.mdx; in-page anchors resolve)<Tabs>/<Tab>/<Accordion>components and nested YAML parse