pulsemcp scanned Safe content atomic mcp-remote

Slack

Slack MCP server implementation by Zencoder AI that provides AI assistants with complete access to Slack workspace operations including channel management, message posting, thread replies, reactions, and user profile retrieval. Built with TypeScript using the modern MCP SDK v1.15.1, the implementation supports both stdio and Streamable HTTP transports with optional Bearer token authentication, handles predefined channel configurations for restricted environments, and includes comprehensive Slack API integration with proper OAuth scope management for channels:read, chat:write, reactions:write, and users:read permissions. The server serves developers building AI-powered Slack bots, teams requiring programmatic workspace management, and organizations needing automated customer support or internal communication workflows that leverage Slack's messaging infrastructure with full thread management and user interaction capabilities.

Cognium trust score

64%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-01.

Scan details: Circle-IR · 2026-09-01 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: communication
Source: PulseMCP
Repository: github.com/zencoderai/slack-mcp-server
Author type: human
Last scanned: 2026-09-01
Updated: 2026-09-01

View source Find related skills

MCP

Resolve Slack from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"