Kjell Tore Guttormsen 2491f5c732 feat: initial companion repo for OpenClaw vs Claude Code article

40 files demonstrating every major OpenClaw capability using Claude Code:
- 3 agents (researcher, writer, reviewer)
- 3 skills (daily-briefing, slack-message, web-research)
- 2 security hooks (pre-tool-use blocker, post-tool-use logger)
- 10 self-contained examples with copy-paste prompts
- Complete feature map (20 capabilities, 11 full match, 7 different, 2 gap)
- Security docs including NemoClaw comparison
- Automation, messaging, browser, memory documentation

Zero dependencies. Clone and run.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-26 09:47:29 +01:00

1.2 KiB

Raw Blame History

name	description
send-slack-message	Send a message to a Slack channel via MCP. Demonstrates multi-channel messaging capability.

Send Slack Message

Send a message to a Slack channel. This demonstrates how Claude Code handles messaging through MCP servers, compared to OpenClaw's 15+ native channel integrations.

Prerequisites

You need a Slack MCP server configured in .mcp.json. Example:

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": ["@anthropic-ai/mcp-slack@latest"],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-token-here"
      }
    }
  }
}

Usage

Tell Claude Code: "Send a message to #general saying [your message]"

Claude Code will use the Slack MCP server's send_message tool.

How this compares to OpenClaw

OpenClaw has native Slack integration (Bolt SDK, no config needed beyond token). Claude Code uses MCP as the integration layer. The result is the same: a message arrives in Slack. The setup differs: OpenClaw is plug-and-play, Claude Code requires MCP configuration.

Other messaging channels

Telegram: Native via Claude Code Channels (v2.1.80+)
Discord: Via MCP server
Email: Via MCP server (e.g., Gmail MCP)
Teams: Via MCP server or webhook

1.2 KiB Raw Blame History