Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Slack ↔ WxO MCP Gateway

by markusvankempenversion 1.0.3i★ 0iRuns on your computerOfficial site ↗
Registry nameio.github.markusvankempen/slack-wxo-mcp-gateway

How to install

What it does

Lifts WxO Slack limits: every-message wake-up, multi-channel MCP. https://markusvankempen.github.io/

  • Connects Runs on your computer
  • Account or key Needs SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET · 1 setting to fill in (WXO_INSTANCE_URL)
  • Category Chat & email

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness3/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score3/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Slack ↔ WxO MCP Gateway. Follow https://mcp.popnx.com/i/markusvankempen-slack-wxo-mcp-gateway.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Slack ↔ WxO MCP Gateway key (create it on the maker’s site) · 1 setting(s) to fill in (WXO_INSTANCE_URL) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Slack ↔ WxO MCP Gateway for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "slack-wxo-gateway": { "command": "npx", "args": [ "-y", "@markusvankempen/slack-wxo-mcp-gateway", "--stdio" ], "env": { "SLACK_BOT_TOKEN": "your-value", "WXO_INSTANCE_URL": "your-value", "WXO_API_KEY": "your-value", "SLACK_SIGNING_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET, WXO_INSTANCE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Slack ↔ WxO MCP Gateway tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Slack ↔ WxO MCP Gateway key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Slack ↔ WxO MCP Gateway site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • WXO_INSTANCE_URL watsonx Orchestrate instance base URL

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "mcpServers": {
        "slack-wxo-gateway": {
          "command": "npx",
          "args": [
            "-y",
            "@markusvankempen/slack-wxo-mcp-gateway",
            "--stdio"
          ],
          "env": {
            "SLACK_BOT_TOKEN": "your-value",
            "WXO_INSTANCE_URL": "your-value",
            "WXO_API_KEY": "your-value",
            "SLACK_SIGNING_SECRET": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Slack ↔ WxO MCP Gateway and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Slack ↔ WxO MCP Gateway or shows a Slack ↔ WxO MCP Gateway tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • WXO_AGENT_ID Default WxO agent id for bindings
  • GATEWAY_TRANSPORT stdio (IDE) or streamable-http (hosted). Default for npx IDE use: stdio

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Slack ↔ WxO MCP Gateway yet

Slack ↔ WxO MCP Gateway runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Slack ↔ WxO MCP Gateway

  • You need a Slack ↔ WxO MCP Gateway key (create it on the maker’s site) · 1 setting(s) to fill in (WXO_INSTANCE_URL) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Slack ↔ WxO MCP Gateway key (create it on the maker’s site) · 1 setting(s) to fill in (WXO_INSTANCE_URL) · Install Node.js on your computer first (one time)
  • You need a Slack ↔ WxO MCP Gateway key (create it on the maker’s site) · 1 setting(s) to fill in (WXO_INSTANCE_URL) · Install Node.js on your computer first (one time)
  • You need a Slack ↔ WxO MCP Gateway key (create it on the maker’s site) · 1 setting(s) to fill in (WXO_INSTANCE_URL) · Install Node.js on your computer first (one time)

B · Others in Chat & email that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Slack ↔ WxO MCP Gateway key (create it on the maker’s site) · 1 setting(s) to fill in (WXO_INSTANCE_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Slack ↔ WxO MCP Gateway for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user slack-wxo-gateway --env SLACK_BOT_TOKEN=your-value --env WXO_INSTANCE_URL=your-value --env WXO_API_KEY=your-value --env SLACK_SIGNING_SECRET=your-value -- npx -y @markusvankempen/slack-wxo-mcp-gateway --stdio 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET, WXO_INSTANCE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Slack ↔ WxO MCP Gateway tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Slack ↔ WxO MCP Gateway key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Slack ↔ WxO MCP Gateway site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • WXO_INSTANCE_URL watsonx Orchestrate instance base URL

    Descriptions are as written by the maker.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    claude mcp add --scope user slack-wxo-gateway --env SLACK_BOT_TOKEN=your-value --env WXO_INSTANCE_URL=your-value --env WXO_API_KEY=your-value --env SLACK_SIGNING_SECRET=your-value -- npx -y @markusvankempen/slack-wxo-mcp-gateway --stdio

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Slack ↔ WxO MCP Gateway listed as connected

  7. Try it

    Use Slack ↔ WxO MCP Gateway and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Slack ↔ WxO MCP Gateway or shows a Slack ↔ WxO MCP Gateway tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • WXO_AGENT_ID Default WxO agent id for bindings
  • GATEWAY_TRANSPORT stdio (IDE) or streamable-http (hosted). Default for npx IDE use: stdio

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Slack ↔ WxO MCP Gateway key (create it on the maker’s site) · 1 setting(s) to fill in (WXO_INSTANCE_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Slack ↔ WxO MCP Gateway for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "slack-wxo-gateway": { "command": "npx", "args": [ "-y", "@markusvankempen/slack-wxo-mcp-gateway", "--stdio" ], "env": { "SLACK_BOT_TOKEN": "your-value", "WXO_INSTANCE_URL": "your-value", "WXO_API_KEY": "your-value", "SLACK_SIGNING_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET, WXO_INSTANCE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Slack ↔ WxO MCP Gateway tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Slack ↔ WxO MCP Gateway key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Slack ↔ WxO MCP Gateway site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • WXO_INSTANCE_URL watsonx Orchestrate instance base URL

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Slack ↔ WxO MCP Gateway settings, SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET, WXO_INSTANCE_URL is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Slack ↔ WxO MCP Gateway and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Slack ↔ WxO MCP Gateway or shows a Slack ↔ WxO MCP Gateway tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • WXO_AGENT_ID Default WxO agent id for bindings
  • GATEWAY_TRANSPORT stdio (IDE) or streamable-http (hosted). Default for npx IDE use: stdio

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Slack ↔ WxO MCP Gateway key (create it on the maker’s site) · 1 setting(s) to fill in (WXO_INSTANCE_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Slack ↔ WxO MCP Gateway for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "slack-wxo-gateway": { "type": "stdio", "command": "npx", "args": [ "-y", "@markusvankempen/slack-wxo-mcp-gateway", "--stdio" ], "env": { "SLACK_BOT_TOKEN": "your-value", "WXO_INSTANCE_URL": "your-value", "WXO_API_KEY": "your-value", "SLACK_SIGNING_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET, WXO_INSTANCE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Slack ↔ WxO MCP Gateway tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Slack ↔ WxO MCP Gateway key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Slack ↔ WxO MCP Gateway site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • WXO_INSTANCE_URL watsonx Orchestrate instance base URL

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Slack ↔ WxO MCP Gateway settings, SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET, WXO_INSTANCE_URL is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    Use Slack ↔ WxO MCP Gateway and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Slack ↔ WxO MCP Gateway or shows a Slack ↔ WxO MCP Gateway tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • WXO_AGENT_ID Default WxO agent id for bindings
  • GATEWAY_TRANSPORT stdio (IDE) or streamable-http (hosted). Default for npx IDE use: stdio

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Slack ↔ WxO MCP Gateway💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user slack-wxo-gateway --env SLACK_BOT_TOKEN=your-value --env WXO_INSTANCE_URL=your-value --env WXO_API_KEY=your-value --env SLACK_SIGNING_SECRET=your-value -- npx -y @markusvankempen/slack-wxo-mcp-gateway --stdio

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "slack-wxo-gateway": {
      "command": "npx",
      "args": [
        "-y",
        "@markusvankempen/slack-wxo-mcp-gateway",
        "--stdio"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "your-value",
        "WXO_INSTANCE_URL": "your-value",
        "WXO_API_KEY": "your-value",
        "SLACK_SIGNING_SECRET": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "slack-wxo-gateway": {
      "command": "npx",
      "args": [
        "-y",
        "@markusvankempen/slack-wxo-mcp-gateway",
        "--stdio"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "your-value",
        "WXO_INSTANCE_URL": "your-value",
        "WXO_API_KEY": "your-value",
        "SLACK_SIGNING_SECRET": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "slack-wxo-gateway": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@markusvankempen/slack-wxo-mcp-gateway",
        "--stdio"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "your-value",
        "WXO_INSTANCE_URL": "your-value",
        "WXO_API_KEY": "your-value",
        "SLACK_SIGNING_SECRET": "your-value"
      }
    }
  }
}

Values you fill in

  • SLACK_BOT_TOKEN secret required env
    Slack Bot User OAuth Token (xoxb-…)
  • WXO_INSTANCE_URL required env
    watsonx Orchestrate instance base URL
  • WXO_API_KEY secret required env
    watsonx Orchestrate / MCSP API key
  • WXO_AGENT_ID env
    Default WxO agent id for bindings
  • GATEWAY_TRANSPORT env
    stdio (IDE) or streamable-http (hosted). Default for npx IDE use: stdio
  • SLACK_SIGNING_SECRET secret required env
    Slack signing secret (Events mode)

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
71/wk
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
1.0.3
Published to registryi
Jul 19, 2026
Code last changedi
Jul 18, 2026
Maker
markusvankempen
Packages
npm: @markusvankempen/slack-wxo-mcp-gateway
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account markusvankempen, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 4 months ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @markusvankempen/slack-wxo-mcp-gateway@1.0.3

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/markusvankempen-slack-wxo-mcp-gateway.svg)](https://mcp.popnx.com/en/servers/markusvankempen-slack-wxo-mcp-gateway)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Chat & emaili

  • More stars than 0% of the other 2027 servers in this category
  • Published to the registry more recently than 14% of the other 2027 servers in this category
  • Basic checks equal to or better than 99% of the other 2027 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Slack ↔ WxO MCP Gateway safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 4 months ago, and the latest version (1.0.3) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostWidely used↓ 5.4K/wk★ 1.4KUpdated 5 days ago

Computer or cloud✓ service owner · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

by infobipEarly★ 36Updated 13 months ago

Runs in the cloud✓ service owner · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

by w1neEarly★ 35Updated 23 days ago

Runs in the cloud✓ service owner · kernelcad.com
Compared with similar ones
This one
Slack ↔ WxO MCP Gateway
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
Runs whereInstalls on your computerCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoYesNo
Basic checks3/35/54/44/44/44/4
LicenseApache-2.0MITAGPL-3.0Apache-2.0MITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Slack ↔ WxO MCP Gateway

Author: Markus van Kempen Email: mvankempen@ca.ibm.com · markus.van.kempen@gmail.com Web: https://markusvankempen.github.io/ · GitHub

npm: @markusvankempen/slack-wxo-mcp-gateway · MCP: io.github.markusvankempen/slack-wxo-mcp-gateway

This GitHub repo is documentation + registry metadata. It does not include the runnable application source.

Install / run via npm: npx -y @markusvankempen/slack-wxo-mcp-gateway · Site: https://markusvankempen.github.io/

Pitch: MCP gateway that lifts watsonx Orchestrate Slack limitations — every-message wake-up, multi-channel→multi-agent routing, clean in-thread replies, and a streamable-http toolkit for WxO + Cursor / VS Code / Bob / Antigravity — without replacing your agents.

tags: wxo-limitations · byo-slack · every-message · multi-channel · multi-agent · thread-followups · gateway-thread · no-done-noise · mcp-toolkit · streamable-http · poller · code-engine · ngrok · agentic-ai

One config site: map many Slack channels → many WxO agents.

Poller (and optional Slack Events) wake agents.

Same host exposes an MCP toolkit (/mcp) for WxO / Cursor / other clients.

Deep dive: [Why this MCP — lifting WxO limits](docs/WHY-THIS-MCP.md)

Architecture at a glance
flowchart LR

subgraph Slack C1["#support"] C2["#orders"] C3["#ops"] end

subgraph Gateway["Slack ↔ WxO MCP Gateway"] Bind["config.yaml bindings"] Poll["Poller / Events"] MCP["/mcp streamable-http"] UI["Admin UI /"] end

subgraph WxO["watsonx Orchestrate"] A1["Agent A"] A2["Agent B"] A3["Agent C"] end

subgraph Clients["MCP clients"] IDE["Cursor / VS Code / Bob / …"] TK["WxO toolkits"] end

C1 & C2 & C3 --> Poll Poll --> Bind Bind --> A1 & A2 & A3 A1 & A2 & A3 -.->|gateway_thread reply| Poll IDE & TK --> MCP UI --> Bind


Why this approach (WxO limits → lift)

WxO / Slack limitTagGateway lift
byo_slack ≈ @mention / DM onlyevery-messagePoller / Events wake agents on every human message
Hard to run many channels → many agentsmulti-channel multi-agentOne bindings table + admin UI
Thread follow-ups easy to dropthread-followupsReads thread replies + context
Noisy finals (done, etc.) in Slackgateway-thread no-done-noiseGateway posts answers; filters noise
Agents need remote tools with real DNSmcp-toolkit streamable-httpHosted /mcp for Orchestrate toolkits
Ops stuck cloning pollersops-self-serveMCP tools + diagnostics + logs
Slack ops only inside Slack/WxO UIide-paritySame tools in Cursor, VS Code, Bob, Antigravity, Claude

WxO stays the brain (LLMs, skills, flows). This gateway is the Slack + routing + MCP edge. Bring-your-own agent frameworks: docs/frameworks/ (LangGraph, LlamaIndex, OpenAI Agents).


npm / MCP identity

npm@markusvankempen/slack-wxo-mcp-gateway
MCP nameio.github.markusvankempen/slack-wxo-mcp-gateway
Topicsmcp · mcp-server · slack · watsonx · watsonx-orchestrate · ibm · wxo · byo-slack · multi-channel · code-engine · streamable-http · cursor · agentic-ai

Full keyword list lives in package.json for npm discoverability.


Publish & run modes (A–D)

One package / one image — pick a mode (see docs/PUBLISH-MODES.md):

flowchart TB

PKG["npm @markusvankempen/slack-wxo-mcp-gateway

  • optional container image"] PKG --> A["A Local HTTP

:3100 UI + /mcp + poller"] PKG --> B["B Podman / Docker :8080"] PKG --> C["C Code Engine HTTPS always-on"] PKG --> D["D IDE stdio Cursor / VS Code / Bob"] A --> N["ngrok demo tunnel"] A & B & C --> R["Remote /mcp clients"] D --> L["Local MCP session"]

ModeCommandUse
A Local HTTP./scripts/run.sh --mode httpUI + /mcp + poller on laptop
B Podman/Docker./scripts/run.sh --mode podmanSame app in a container
C Code Engine./scripts/run.sh --mode ceAlways-on HTTPS
D IDE MCP./scripts/run.sh --mode ideCursor / VS Code stdio snippets (+ --exec)
Ngrok demo./scripts/run.sh --mode ngrokA + tunnel + WxO toolkit
./scripts/run.sh --mode ide      # print Cursor + VS Code mcp.json

./scripts/run.sh --mode http # local host :3100 ./scripts/run.sh --mode podman # container :8080 ./scripts/run.sh --mode ce # IBM Code Engine

Deep guides: docs/local-ngrok/ · docs/code-engine/ · docs/ide/ Index: docs/README.md · Setup: SETUP.md

Copy-paste IDE JSON: examples/mcp/

Agent frameworks (LangGraph · LlamaIndex · OpenAI Agents)

Connect frameworks to this MCP — do not embed them in the gateway.

GuideFocus
docs/frameworks/Index + checklist
docs/frameworks/langgraph.mdLangGraph / LangChain
docs/frameworks/llamaindex.mdLlamaIndex
docs/frameworks/openai-agents.mdOpenAI Agents SDK
Install (npm / npx) — not from this repo
# Hosted HTTP + admin UI (default)

npx -y @markusvankempen/slack-wxo-mcp-gateway

IDE / stdio MCP

npx -y @markusvankempen/slack-wxo-mcp-gateway --stdio

Requires Node 18+ and Python 3.10+. Env template: .env.example. Guides: local-ngrok · code-engine.


Mental model

Multi-channel routing:

flowchart LR

S1["#support"] --> G["Gateway bindings"] S2["#orders"] --> G S3["#ops"] --> G G --> WA["WxO agent A"] G --> WB["WxO agent B"] G --> WC["WxO agent C"]

Message path (reply_mode: gateway_thread):

sequenceDiagram

participant U as Slack user participant Ch as Channel / thread participant GW as Gateway poller participant Wx as WxO Runs API participant Bot as Slack bot reply

U->>Ch: Human message GW->>Ch: Read new messages / replies GW->>Wx: Start bound agent run Wx-->>GW: Agent answer text GW->>Bot: chat.postMessage in thread Bot-->>Ch: Clean reply (no done noise)

Same host also serves MCP at /mcp and the admin UI at /.


Config (config.yaml)

FieldMeaning
slack_channel_ide.g. C0BHWEZ7NLC
wxo.agent_idTarget Orchestrate agent
modepoll \events \both
reply_modegateway_thread = gateway posts Slack thread after Runs API; agent_tools = only start agent
poll_sec / lookback_secPoller timing

Secrets: use ${ENV_VAR} (loaded from .env).


Endpoints

PathRole
/Admin UI
/mcpMCP streamable HTTP
/slack/eventsSlack Event Subscriptions
/healthLiveness
/api/logsLog ring buffer
/api/toolsMCP tool catalog
/api/diagnosticsSlack + WxO checks
/api/pollOne poll cycle
/api/configMasked JSON / raw YAML
Admin dashboard auth
GATEWAY_ADMIN_USER=admin

GATEWAY_ADMIN_PASSWORD=choose-a-strong-password

Protects / and /api/*. Public: /health, /mcp, /slack/events.

IBM Code Engine
./deploy_code_engine.sh

./test_code_engine.sh

Register the toolkit:

orchestrate toolkits add -k mcp -n slack_wxo_gateway \

--url "https://YOUR-HOST/mcp" \ --transport streamable_http \ --tools "*"

MCP tools (14)

Config: list_bindings, upsert_binding Slack: list_slack_channels, list_recent_messages, list_thread_replies, get_message_context, post_thread_reply, set_typing_indicator WxO: list_wxo_agents, invoke_wxo_agent Ops: poll_once, get_gateway_status, get_recent_logs, run_diagnostics_tool

Bot scopes: channels:read, groups:read, reactions:write (reinstall Slack app after adding).

Agents:

AgentRole
agent.yaml → slack_gateway_test_agentFull-toolkit smoke
agents/slack_gateway_ops_agent.yamlDay-2 ops / routing
agents/slack_gateway_answer_agent.yamlChannel answers (gateway_thread)

Setup (Slack + WxO): SETUP.md — also live in admin UI → Setup Use cases + test plan: USE_CASES.md Publish (npm / GitHub): PUBLISH.md


Reply modes

`gateway_thread` (default) — poller/Events → Runs API → gateway chat.postMessage in thread. Use the answer-only agent (no done).

`agent_tools` — gateway only starts the agent; agent uses its own Slack tools.


Cursor / VS Code / Bob / Antigravity / Claude

See [`docs/ide/`](docs/ide/) for each client. Quick remote bridge:

{

"mcpServers": { "slack-wxo-gateway": { "command": "npx", "args": ["-y", "mcp-remote", "https://YOUR-HOST/mcp"] } } }

Package identity:


License

Apache-2.0 — © Markus van Kempen https://markusvankempen.github.io/ · https://github.com/markusvankempen