MCP.Market

Slack ↔ WxO MCP Gateway MCP server

by markusvankempen·io.github.markusvankempen/slack-wxo-mcp-gateway·v1.0.3
No reviews yet

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

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
Growing

0 stars68 downloads/wk

Reviews

Write one

Nobody has reviewed Slack ↔ WxO MCP Gateway yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Slack ↔ WxO MCP Gateway tools (14, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_gateway_status

    Health + binding counts + poller state.

  • get_message_context

    Fetch parent + recent thread replies as a prompt context pack. Useful for follow-ups so the agent sees full thread history.

  • get_recent_logs

    Return recent gateway log lines from the in-memory ring buffer.

  • invoke_wxo_agent

    Invoke a watsonx Orchestrate agent via the Runs API.

  • list_bindings

    List configured Slack channel → WxO agent bindings (secrets masked).

  • list_recent_messages

    List recent Slack messages in a channel (debug / agent use).

  • list_slack_channels

    List Slack channels the bot can see (id + name) for binding setup. Needs scopes: channels:read, groups:read (for private).

  • list_thread_replies

    List replies in a Slack thread (includes parent as first message).

  • list_wxo_agents

    List watsonx Orchestrate agents (id, name, description) for binding picker. Uses the binding's WxO creds if channel_id is set, else wxo_defaults.

  • poll_oncewrite action

    Run one poll cycle for a channel (or all poll bindings). Useful for schedulers / manual wake-up.

  • post_thread_replywrite action

    Post a threaded Slack reply under thread_ts.

  • run_diagnostics_toolwrite action

    Run Slack auth + WxO token (+ optional invoke) diagnostic checks.

  • set_typing_indicator

    Show/hide a 'thinking' reaction on a Slack message (bots have no channel typing API). Requires reactions:write. Default emoji: hourglass_flowing_sand.

  • upsert_binding

    Add or update a Slack channel → WxO agent binding in config.yaml. Match by slack_channel_id (preferred) or name. Poller reloads next cycle.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan24 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 69 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Slack ↔ WxO MCP Gateway compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 50% of 1,119 Developer tools servers
Tools
14
the typical Developer tools server has 7
Tools that change things
21%
typical: 5%. Fewer write tools means less an agent can break
Downloads a week
68
more than 48% of 436 Developer tools servers with a package

What its tools let an agent do: 9 read · 2 change · 1 send or post · 2 run or deploy

Install Slack ↔ WxO MCP Gateway in Claude Code, Cursor or VS Code

Runs npx -y @markusvankempen/slack-wxo-mcp-gateway on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add slack-wxo-mcp-gateway -- npx -y @markusvankempen/slack-wxo-mcp-gateway
Add to Cursor

What the publisher says

From the Slack ↔ WxO MCP Gateway repository's README, as published. We do not edit it. Read it on GitHub

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

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 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

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):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Slack ↔ WxO MCP Gateway: common questions

Is Slack ↔ WxO MCP Gateway MCP server safe?
Mostly: it is graded B (78/100). Read the Slack ↔ WxO MCP Gateway safety report
How do I install Slack ↔ WxO MCP Gateway?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Slack ↔ WxO MCP Gateway need an API key?
Yes. The registry entry asks for SLACK_BOT_TOKEN, WXO_API_KEY, SLACK_SIGNING_SECRET.
Is Slack ↔ WxO MCP Gateway maintained?
The last commit was 109 days ago (2026-07-18). The latest release is v1.0.3.
What can I use instead of Slack ↔ WxO MCP Gateway?
Servers from other publishers that do the same job: Graphql Enhanced MCP server, Scrapling MCP Server and GitDiagram MCP server.
How does Slack ↔ WxO MCP Gateway compare with other Developer tools MCP servers?
safety score 78/100 (higher than 50% of 1,119 Developer tools servers); tools 14 (the typical Developer tools server has 7); tools that change things 21% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Slack ↔ WxO MCP Gateway

Same job from other publishers: the closest match first, then the best rated.

  • Graphql Enhanced
    GraphQL gateway for LLMs. Handles huge GitHub GraphQL & @neo4j/graphql schemas without crashing
    A
  • Scrapling MCP Server
    Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
    A
  • GitDiagram
    Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
    A
  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B

More from markusvankempen →