@capybara-hq/plugin-slack 0.1.0-rc.1 → 0.1.0-rc.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,19 +1,37 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
3
  "name": "slack",
4
- "version": "0.1.0-rc.1",
4
+ "version": "0.1.0-rc.11",
5
5
  "publisher": "Capybara",
6
6
  "description": "Slack (channel@1 bot over Socket Mode with Block Kit cards, identity-source@1 Sign in with Slack, directory@1)",
7
7
  "displayName": {
8
8
  "zh": "Slack",
9
9
  "en": "Slack"
10
10
  },
11
+ "icon": "./icon.svg",
11
12
  "homepage": "https://github.com/capybara-hq/plugins/tree/main/plugins/slack#readme",
13
+ "dependencies": [
14
+ {
15
+ "name": "connector-mcp",
16
+ "version": "^0.1.0-rc.1"
17
+ }
18
+ ],
19
+ "setupGuides": [
20
+ {
21
+ "id": "slack-app",
22
+ "place": "channel-connection"
23
+ },
24
+ {
25
+ "id": "slack-connector",
26
+ "place": "connector-template",
27
+ "template": "slack"
28
+ }
29
+ ],
12
30
  "extension": {
13
31
  "entry": "./dist/index.mjs",
14
32
  "manifest": {
15
33
  "name": "slack",
16
- "version": "0.1.0-rc.1",
34
+ "version": "0.1.0-rc.11",
17
35
  "sdk": "^0.1.0-rc.0",
18
36
  "provides": [
19
37
  "channel@1",
@@ -26,6 +44,11 @@
26
44
  "network": [
27
45
  "slack.com",
28
46
  "wss-primary.slack.com"
47
+ ],
48
+ "setupChecks": [
49
+ "bot-token",
50
+ "bot-scopes",
51
+ "app-token"
29
52
  ]
30
53
  },
31
54
  "config": {
@@ -128,9 +151,15 @@
128
151
  "label": {
129
152
  "zh": "工作区 ID",
130
153
  "en": "Workspace ID"
131
- }
154
+ },
155
+ "help": {
156
+ "zh": "选填:和机器人令牌一起用于把 Slack 成员同步到组织;只用机器人收发消息时不用填。",
157
+ "en": "Optional: used with the bot token to sync Slack members into the org. Leave empty if you only use the bot for chat."
158
+ },
159
+ "placeholder": "T0123ABCD"
132
160
  },
133
- "title": "Workspace ID"
161
+ "title": "Workspace ID",
162
+ "description": "Optional: used with the bot token to sync Slack members into the org. Leave empty if you only use the bot for chat."
134
163
  },
135
164
  "botToken": {
136
165
  "type": "string",
@@ -140,9 +169,15 @@
140
169
  "label": {
141
170
  "zh": "机器人令牌",
142
171
  "en": "Bot token"
143
- }
172
+ },
173
+ "help": {
174
+ "zh": "选填,仅用于成员同步;聊天用的令牌在新建渠道连接时填。",
175
+ "en": "Optional, only for member sync. The tokens for chat go into the channel connection you create under Channels."
176
+ },
177
+ "placeholder": "xoxb-…"
144
178
  },
145
- "title": "Bot token"
179
+ "title": "Bot token",
180
+ "description": "Optional, only for member sync. The tokens for chat go into the channel connection you create under Channels."
146
181
  }
147
182
  }
148
183
  }
package/README.md CHANGED
@@ -1,12 +1,15 @@
1
1
  # @capybara-hq/plugin-slack
2
2
 
3
- The official Slack plugin. It provides three capabilities:
3
+ The official Slack plugin. It provides three capabilities and a connector template:
4
4
 
5
5
  - `channel@1` (bot): receives events over [Socket Mode](https://docs.slack.dev/apis/events-api/using-socket-mode)
6
6
  (no public callback URL needed), sends messages through the Web API, and renders approval / question /
7
7
  connection / binding cards as Block Kit.
8
8
  - `identity-source@1` (Sign in with Slack, OpenID Connect): sign in to Capybara with a Slack account.
9
9
  - `directory@1` (directory sync): syncs Slack workspace members into org members.
10
+ - The connector template `slack` ([Slack connector](#slack-connector-slacks-mcp-server)): agents search,
11
+ read and send in Slack **as the person talking to them**, through Slack's MCP server and each member's own
12
+ OAuth authorization. Switched off by default.
10
13
 
11
14
  All three use the same identity key: `identities.source` = `slack:<team id>`, `external_id` = the Slack user id (`U…`).
12
15
  When the same person appears through sign-in, a DM to the bot and directory sync, it maps to one identity row and one account.
@@ -15,26 +18,39 @@ The Slack docs cited here were consulted on 2026-10-20.
15
18
 
16
19
  ## Create the Slack app
17
20
 
18
- 1. Open <https://api.slack.com/apps> → **Create New App** → **From a manifest**, pick the workspace, and paste this directory's
19
- [`app-manifest.yaml`](./app-manifest.yaml) (format: [App manifest reference](https://docs.slack.dev/reference/app-manifest)).
20
- It turns on Socket Mode and Interactivity, subscribes to the events `message.im`, `app_mention`, `message.channels`,
21
- `message.groups`, `team_join` and `user_change`, and requests these bot scopes:
22
-
23
- | scope | Purpose |
24
- |---|---|
25
- | `chat:write` | Send and update replies and cards |
26
- | `im:history` | Receive DM messages |
27
- | `app_mentions:read` | Receive messages that @-mention the bot in channels |
28
- | `channels:history` / `groups:history` | Receive thread replies in public / private channels |
29
- | `users:read` | Look up the speaker's display name and avatar; people-change events; directory `users.list` |
30
- | `users:read.email` | Read emails during directory sync (the bot itself does not use it) |
31
-
32
- 2. **Basic Information → App-Level Tokens → Generate Token and Scopes**: add the scope `connections:write`
33
- to get the app-level token `xapp-…` (Socket Mode uses it to call `apps.connections.open`).
34
- 3. **Install App → Install to Workspace** to get the bot token `xoxb-…`.
35
- 4. In the Capybara org settings, enable the `slack` plugin, then **create a new channel connection**: pick Slack as the plugin, fill in `appToken` (`xapp-…`) and
36
- `botToken` (`xoxb-…`), and bind an agent. Both are stored in the secret store, and the API only returns "set".
37
- 5. In Slack, DM the bot, or add the bot to a channel and @-mention it. The first conversation gets a binding card; click the button to confirm the binding on the web page.
21
+ The steps live in the product: the plugin ships the setup guide `slack-app`
22
+ ([`guides/slack-app.md`](./guides/slack-app.md), Chinese
23
+ [`guides/slack-app.zh.md`](./guides/slack-app.zh.md)). When an org admin creates a Slack channel
24
+ connection (Channels → New channel) or opens one, the web app shows the guide for the connection's
25
+ inbound mode (Socket Mode or webhook) with the app manifest filled in for that connection (its name,
26
+ the Sign in with Slack callback and, in webhook mode, its webhook URL) and a copy button. When a
27
+ plugin upgrade changes the manifest, the channel page says so and asks you to update the Slack app.
28
+ To preview the guide outside Capybara, run
29
+ `capybara-plugin guide slack-app --mode long_connection` (or `--mode webhook`, `--locale zh`) in
30
+ this repository.
31
+
32
+ The guide carries live checks, run when the page is viewed (cached for five minutes) or on
33
+ **Check again**:
34
+
35
+ | Check | What it does |
36
+ |---|---|
37
+ | `bot-token` | `auth.test` with the connection's bot token: refused (`invalid_auth`, `token_revoked`, …), wrong token type or an org-wide install is failing with the fix |
38
+ | `bot-scopes` | Compares the scopes Slack reports for the bot token (`x-oauth-scopes`) with the manifest's bot scopes and names the missing ones |
39
+ | `app-token` | `apps.connections.open` with the app-level token (Socket Mode only; the socket is never opened) |
40
+
41
+ Each check makes one read-only call, passes the kernel's abort signal on and never retries; rate
42
+ limits and Slack outages answer "unknown", never "failing". The guide also uses the kernel checks
43
+ `capybara:public-url`, `capybara:webhook-public` and `capybara:webhook-received`.
44
+
45
+ Notes for operators:
46
+
47
+ - The org must enable the `slack` plugin before it can create a connection (its org-level fields are
48
+ optional and only for [directory sync](#directory-directory1)). The tokens are stored in the
49
+ secret store, and the API only returns "set".
50
+ - The app's name in the manifest is the connection's name; Slack caps it at 35 characters, so shorten it in
51
+ the app settings if Slack refuses it (the bot user's name stays `capybara`).
52
+ - In Slack, DM the bot, or add the bot to a channel and @-mention it. The first conversation gets a
53
+ binding card; click the button to confirm the binding on the web page.
38
54
 
39
55
  Note: apps that use Socket Mode cannot currently be listed in the public Slack Marketplace, and one app can hold at most 10 concurrent
40
56
  Socket Mode connections ([Using Socket Mode](https://docs.slack.dev/apis/events-api/using-socket-mode)). At any moment Capybara has only one
@@ -54,10 +70,15 @@ connection → Overview → Inbound mode); the connection page then shows its we
54
70
  1. Copy **Basic Information → App Credentials → Signing Secret** into the connection's
55
71
  `signingSecret`. Every request is verified with it (HMAC-SHA256 over `v0:<timestamp>:<body>`)
56
72
  and must be at most 5 minutes old; without it every webhook request is refused.
57
- 2. In the app settings, turn **Socket Mode** off, then use the webhook URL as the **Event
58
- Subscriptions → Request URL** (Slack verifies it with a `url_verification` challenge, which the
59
- plugin answers) and as the **Interactivity & Shortcuts → Request URL** (card buttons).
60
- 3. `appToken` is optional in webhook mode: only Socket Mode uses it.
73
+ 2. The webhook manifest of the setup guide turns **Socket Mode** off and uses the connection's webhook
74
+ URL as the **Event Subscriptions → Request URL** (Slack verifies it with a `url_verification`
75
+ challenge, which the plugin answers), the **Interactivity & Shortcuts → Request URL** (card
76
+ buttons) and each slash command's **Request URL**. For an existing app, paste it under **App
77
+ Manifest**, or set the four URLs by hand. The plugin tells a slash command from an event by its
78
+ form body and answers it like Socket Mode does.
79
+ 3. The webhook URL exists only once the connection is saved, so the guide shows it after saving;
80
+ create the connection first, then let Slack verify the URL.
81
+ 4. `appToken` is optional in webhook mode: only Socket Mode uses it.
61
82
 
62
83
  Both modes parse events the same way (same message and card-click ids), so the kernel's dedupe
63
84
  still drops a redelivery that arrives across a mode switch.
@@ -66,7 +87,7 @@ still drops a redelivery that arrives across a mode switch.
66
87
 
67
88
  [Sign in with Slack](https://docs.slack.dev/authentication/sign-in-with-slack/) is based on OpenID Connect.
68
89
 
69
- 1. In the app settings, add
90
+ 1. The setup guide's manifest already lists the callback; otherwise, in the app settings, add
70
91
  `<http.publicUrl>/api/v1/auth/sso/slack/callback` under **OAuth & Permissions → Redirect URLs** (for example `https://capybara.example.com/api/v1/auth/sso/slack/callback`;
71
92
  the `redirect_uri` the kernel sends must equal it or be a sub-path of it).
72
93
  2. The login flow requests the scopes `openid`, `email` and `profile` in the authorization URL (`openid` is required; `email` gives the email and
@@ -114,6 +135,107 @@ channel connection uses, but the config is stored separately and goes through th
114
135
  - When `teamId` / `botToken` are not filled in (the org only uses the bot), the plugin's `configured()` returns false: the kernel does not scan or sync, and records no audit
115
136
  or warning; a manual sync returns 409 `directory.not_configured`. It is not treated as an empty directory.
116
137
 
138
+ ## Slack connector (Slack's MCP server)
139
+
140
+ The template [`connectors/slack.json`](./connectors/slack.json) connects Slack's official MCP server
141
+ (`https://mcp.slack.com/mcp`, [Slack MCP server](https://docs.slack.dev/ai/slack-mcp-server/)) through the
142
+ `connector-mcp` plugin (a dependency in `plugin.json`, preinstalled with Capybara). Each member authorizes
143
+ their own Slack account, so an agent sees and does exactly what that person may in Slack, and every call runs
144
+ on the caller's own user token; there is no shared org token. Design and decisions:
145
+ [docs/superpowers/specs/2026-11-08-slack-connector-design.md](https://github.com/capybara-hq/plugins/blob/main/docs/superpowers/specs/2026-11-08-slack-connector-design.md).
146
+
147
+ - **Off by default** (`defaultEnabled: false`): an org that turns on the `slack` plugin for the bot does not
148
+ see the connector until an org admin switches the template on and enters the OAuth client.
149
+ - **Auth**: OAuth authorization code, personal credentials, MCP discovery (Slack's metadata points at
150
+ `https://slack.com/oauth/v2_user/authorize` and `oauth.v2.user.access`), a manually entered client (Slack
151
+ offers no dynamic client registration), `client_secret_post`, and 30 explicit user scopes (the full set
152
+ Slack's server supports; a scope Slack adds later needs a template update).
153
+ - **Tools**: reads are allowed; every write (send, schedule, draft, create, update, react, upload) and
154
+ `slack_search_public_and_private` (reaches DMs and private channels) ask the person first. Org admins and
155
+ agents change the policies on the tools page; tools Slack adds later default by their annotations (`ask`
156
+ without `readOnlyHint`).
157
+
158
+ ### Set it up
159
+
160
+ The connector template carries the setup guide `slack-connector`
161
+ ([`guides/slack-connector.md`](./guides/slack-connector.md), Chinese
162
+ [`guides/slack-connector.zh.md`](./guides/slack-connector.zh.md)), shown on the template's pages:
163
+ org admins see how to create the internal Slack app (the manifest with this deployment's OAuth
164
+ callback filled in), keep it internal and enter its client id and secret; members see how to connect
165
+ their own Slack account. Preview it with
166
+ `capybara-plugin guide slack-connector --audience admin` (or `--audience member`). Its rows are
167
+ kernel checks: `capybara:public-url`, `capybara:oauth-client`, `capybara:oauth-token-endpoint`
168
+ (the stored client against Slack's token endpoint; the secret stays in the kernel),
169
+ `capybara:connector-tools` and, for members, `capybara:connector-connected`.
170
+
171
+ Notes for operators:
172
+
173
+ - The deployment must set `http.publicUrl`: the OAuth callback is
174
+ `<http.publicUrl>/api/v1/oauth/callback`.
175
+ - Each org enters its own client (the same Slack app may serve several orgs); rotate the secret later
176
+ through the connector's org credentials.
177
+ - Capybara stays a confidential client: it still sends a PKCE challenge (Slack's metadata advertises
178
+ it), but PKCE must not be enabled in the app settings.
179
+
180
+ ### Decided risks
181
+
182
+ - **Slack data in conversations**: tool results stay in the conversation event log and archives like any
183
+ other connector's, although Slack's Real-time Search terms say retrieved data must not be stored. The app
184
+ is the customer's own internal app under its own Slack agreement.
185
+ - **Quoting private Slack content into shared threads**: in a Slack channel thread (through the bot), a tool
186
+ call runs on the acting member's token and the reply goes to a channel others read. There is no special
187
+ rule for this; it relies on the tool policies (the `ask` default of `slack_search_public_and_private`
188
+ plus whatever the org or agent sets).
189
+ - **No identity check**: a member may connect a different Slack account than the one bound to their
190
+ Capybara account; the token still reaches only their own calls.
191
+ - **No revoke on disconnect** and **one client per org** (no platform-level client) in this release.
192
+ - **Scopes**: the full set only; there is no reduced variant (for example without DM scopes).
193
+
194
+ ## Commands
195
+
196
+ The kernel parses commands from the message text: `/new` (DM: start a new conversation), `/env [name]`
197
+ (DM: list or set your default environment) and `/<skill> args` (invoke a skill). The Slack client,
198
+ however, treats any message starting with `/` as a slash command and refuses names no app registered
199
+ ("/env is not a valid command"), so those messages never reach the bot. The app therefore registers
200
+ three slash commands, and the plugin turns each back into the text the kernel parses (it parses no
201
+ command itself):
202
+
203
+ | Slash command | Text the kernel gets |
204
+ |---|---|
205
+ | `/new` | `/new` |
206
+ | `/env [name]` | `/env [name]` |
207
+ | `/capybara <skill> [args]` | `/<skill> [args]` (`/capybara fix-issue 12` → `/fix-issue 12`; also `/capybara github:fix-issue 12`) |
208
+
209
+ `@capybara /fix-issue 12` in a channel still works as plain text, as before. Commands other than `/new`
210
+ and `/env` map like `/capybara`, so an admin may rename it (for example when another app already owns
211
+ `/capybara`). Slack lets several apps register `/new` or `/env`; a person who has two such apps picks
212
+ one in Slack's menu.
213
+
214
+ - **In your DM with the bot**: the command becomes a DM message from you, exactly as if you had typed
215
+ the text (binding, `/new`, `/env` and skills behave the same). Slack shows no slash command in the
216
+ conversation, so the ack carries an ephemeral echo of what you ran ("only visible to you"); the
217
+ kernel's reply follows as usual. The message id is `<DM channel>:cmd-<trigger_id>`.
218
+ - **In a channel**: the bot first posts a visible echo `@you: /capybara fix-issue 12` and the event is
219
+ that message, with `mentionsBot: true` (the same as `@capybara /fix-issue 12`): the kernel applies its
220
+ group rules (`/new` and `/env` are plain text in a group) and replies in the echo's thread, where you
221
+ can follow up by @-mentioning the bot. The bot must be in the channel; otherwise you get an
222
+ ephemeral "invite the app first" hint and nothing is sent to the kernel.
223
+ - **In a DM between two people** (where the bot cannot reply): an ephemeral hint to use your DM with
224
+ the app or a channel; nothing is sent. The plugin finds the bot's own DM with `conversations.open`
225
+ (cached in kv for a day; if the lookup fails it assumes the DM is the bot's).
226
+ - **`/capybara` without a skill**: an ephemeral usage line.
227
+ - **Ack**: Slack wants a slash command acked within 3 seconds and never redelivers one. The plugin acks
228
+ only after `onEvent` resolves, which is quick (the kernel dedupes and enqueues); before it, at most
229
+ one Web API call runs (the echo post, or the DM lookup), each with a 1.5 second timeout, in parallel
230
+ with the profile lookup. If `onEvent` rejects, nothing is acked and Slack shows the person a timeout
231
+ error, so they run the command again. A Socket Mode redelivery of the same command (same
232
+ `trigger_id`) reuses the cached echo, so it is posted once.
233
+ - The fixed hints are bilingual (English · 中文): the org's IM language is not known on inbound.
234
+
235
+ Existing apps: re-paste the manifest from the setup guide (**App Manifest** in the app settings) or add the three commands
236
+ by hand under **Slash Commands**, add the bot scopes `commands` and `im:write`, then **reinstall the
237
+ app** to the workspace (Slack asks for it because the scopes changed). The bot token stays the same.
238
+
117
239
  ## Behavior
118
240
 
119
241
  - **DMs**: every text message goes to the kernel. **Channels**: only messages that @-mention the bot (a new message gets a thread reply under it), and replies inside threads
@@ -135,8 +257,15 @@ channel connection uses, but the config is stored separately and goes through th
135
257
  - **Reconnect**: managed by the plugin (SDK auto-reconnect is turned off). When Slack recycles a connection normally it reconnects immediately; consecutive short-lived (under 10 seconds) connections back off exponentially
136
258
  (with jitter), and after 5 in a row, or on receiving `link_disabled`, it reports an error; the kernel records `last_error` and backs off.
137
259
  - **Idempotency**: `chat.postMessage` has no idempotency parameter, so `idempotencyKey` is ignored.
138
- - **Profile**: the display name / avatar come from the `user_profile` carried by the event, otherwise from `users.info` (cached per process for 10 minutes, at most 1000 people,
139
- 1.5 second timeout; if the lookup fails it is left out).
260
+ - **Profile, time zone and language**: every speaker is looked up with
261
+ [`users.info`](https://docs.slack.dev/reference/methods/users.info) `include_locale=true` (Tier 4, `users:read`):
262
+ `user.tz` becomes `sender.timeZone` and `user.locale` becomes `sender.locale`, passed as is (the kernel
263
+ ignores an unknown zone and normalizes the language; both win over the person's Capybara settings for the
264
+ run's date, zone and language). The display name and avatar come from the event's `user_profile` when it
265
+ has one, else from the same lookup. The result is cached in the plugin kv per team and user for 10 minutes
266
+ (shared by every replica; nothing in process memory; an unknown user is cached as empty). The lookup has a
267
+ 1.5 second timeout so the 3 second ack deadline holds; on any failure the fields are left out and nothing
268
+ is cached.
140
269
  - **Permission manifest**: `network: ["slack.com", "wss-primary.slack.com"]`, shown only and not enforced; login (OIDC) and the directory also use
141
270
  `slack.com`. The WSS host for Socket Mode is
142
271
  assigned by Slack and is not fixed (for example `wss-primary.slack.com`, `wss-backup.slack.com`, `wss-111.slack.com`); the manifest's domain
@@ -146,9 +275,13 @@ channel connection uses, but the config is stored separately and goes through th
146
275
 
147
276
  | Field | Description |
148
277
  |---|---|
149
- | `botToken` | Bot token (`xoxb-…`, secret) |
150
- | `appToken` | App-level token (`xapp-…`, secret); required for Socket Mode, unused in webhook mode |
151
- | `signingSecret` | Signing Secret (secret); required in webhook mode, unused with Socket Mode |
278
+ Shown in the form with zh / en labels and help.
279
+
280
+ | Field | Label | Description |
281
+ |---|---|---|
282
+ | `appToken` | App-level token / 应用令牌 | `xapp-…` (secret); required for Socket Mode (Basic Information → App-Level Tokens, scope `connections:write`), unused in webhook mode |
283
+ | `botToken` | Bot token / 机器人令牌 | `xoxb-…` (secret; Install App → Bot User OAuth Token) |
284
+ | `signingSecret` | Signing secret / 签名密钥 | Secret; only needed in webhook mode, leave empty for Socket Mode |
152
285
 
153
286
  ## Deployment-level config
154
287
 
@@ -165,5 +298,13 @@ The deployment-level config lives under the kernel config `extensionConfig.slack
165
298
 
166
299
  | Field | Description |
167
300
  |---|---|
168
- | `teamId` | The Slack workspace id for directory sync (`T…`) |
169
- | `botToken` | The bot token for directory sync (`xoxb-…`, secret) |
301
+ | `teamId` | Optional: the Slack workspace id (`T…`) for syncing members into the org; leave empty if you only chat with the bot |
302
+ | `botToken` | Optional, only for member sync (`xoxb-…`, secret); the tokens for chat go into the channel connection |
303
+
304
+ ## Icon
305
+
306
+ `icon.svg`: the Slack mark (owner: Slack (Salesforce)), downloaded on 2026-11-08 from the Slack media kit,
307
+ https://slack.com/media-kit (Logos: https://salesforce.widencollective.com/c/yn6bxnam, file
308
+ SLA-Slack-icon-RGB.svg). It is a trademark of its owner, used only to identify the service this
309
+ plugin connects to; the plugin is not affiliated with or endorsed by the owner. The artwork is
310
+ unchanged except for removing editor metadata and setting a square viewBox.
@@ -155,7 +155,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
155
155
  SOFTWARE.
156
156
 
157
157
  ------------------------------------------------------------------------
158
- jose@6.2.12 (MIT)
158
+ jose@6.2.17 (MIT)
159
159
 
160
160
  The MIT License (MIT)
161
161
 
@@ -269,7 +269,7 @@ Felix Geisendörfer (felix@debuggable.com)
269
269
  THE SOFTWARE.
270
270
 
271
271
  ------------------------------------------------------------------------
272
- undici@8.12.3 (MIT)
272
+ undici@8.12.4 (MIT)
273
273
 
274
274
  MIT License
275
275
 
@@ -0,0 +1,85 @@
1
+ {
2
+ "displayName": {
3
+ "zh": "Slack",
4
+ "en": "Slack"
5
+ },
6
+ "description": "Search, read and send Slack messages, canvases, lists and files as the connected person, through Slack's MCP server. Each member connects their own Slack account; an org admin enters the OAuth client of the company's internal Slack app.",
7
+ "icon": "./icon.svg",
8
+ "defaultEnabled": false,
9
+ "template": {
10
+ "plugin": "connector-mcp",
11
+ "pluginVersion": "^0.1.0-rc.1",
12
+ "connector": "mcp",
13
+ "endpoint": {
14
+ "url": "https://mcp.slack.com/mcp"
15
+ },
16
+ "auth": {
17
+ "type": "oauth_code",
18
+ "ownership": "personal",
19
+ "discovery": "mcp",
20
+ "client": "manual",
21
+ "tokenAuthMethod": "client_secret_post",
22
+ "scopes": [
23
+ "search:read.public",
24
+ "search:read.private",
25
+ "search:read.mpim",
26
+ "search:read.im",
27
+ "search:read.files",
28
+ "search:read.users",
29
+ "channels:history",
30
+ "groups:history",
31
+ "mpim:history",
32
+ "im:history",
33
+ "channels:read",
34
+ "groups:read",
35
+ "mpim:read",
36
+ "im:read",
37
+ "channels:write",
38
+ "groups:write",
39
+ "mpim:write",
40
+ "im:write",
41
+ "chat:write",
42
+ "canvases:read",
43
+ "canvases:write",
44
+ "lists:read",
45
+ "lists:write",
46
+ "files:read",
47
+ "files:write",
48
+ "reactions:read",
49
+ "reactions:write",
50
+ "emoji:read",
51
+ "users:read",
52
+ "users:read.email"
53
+ ]
54
+ },
55
+ "defaultToolPolicies": {
56
+ "slack_search_public": "allow",
57
+ "slack_search_channels": "allow",
58
+ "slack_search_users": "allow",
59
+ "slack_search_emojis": "allow",
60
+ "slack_read_channel": "allow",
61
+ "slack_read_thread": "allow",
62
+ "slack_read_canvas": "allow",
63
+ "slack_read_file": "allow",
64
+ "slack_read_list": "allow",
65
+ "slack_read_user_profile": "allow",
66
+ "slack_list_user_channels": "allow",
67
+ "slack_list_channel_members": "allow",
68
+ "slack_get_reactions": "allow",
69
+ "slack_search_public_and_private": "ask",
70
+ "slack_send_message": "ask",
71
+ "slack_schedule_message": "ask",
72
+ "slack_send_message_draft": "ask",
73
+ "slack_create_conversation": "ask",
74
+ "slack_add_reaction": "ask",
75
+ "slack_create_canvas": "ask",
76
+ "slack_update_canvas": "ask",
77
+ "slack_create_list": "ask",
78
+ "slack_add_list_record": "ask",
79
+ "slack_update_list": "ask",
80
+ "slack_update_list_record": "ask",
81
+ "slack_get_file_upload_url": "ask",
82
+ "slack_complete_file_upload": "ask"
83
+ }
84
+ }
85
+ }