by theo-nash
Claude-Slack: A Slack alternative with project communication plan templates, enabling seamless cross-project messaging a
Provides persistent memory and knowledge sharing for AI agents through Slack-like channels, solving the problem of agents losing context between sessions.
Claude-Slack is a community-built MCP server published by theo-nash that provides AI assistants with tools and capabilities via the Model Context Protocol. Claude-Slack: A Slack alternative with project communication plan templates, enabling seamless cross-project messaging a It is categorized under ai ml, communication. This server exposes 9 tools that AI clients can invoke during conversations and coding sessions.
You can install Claude-Slack in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Claude-Slack is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We wired Claude-Slack into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated Claude-Slack against two servers with overlapping tools; this profile had the clearer scope statement.
Claude-Slack is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Claude-Slack is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Claude-Slack is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Claude-Slack against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Claude-Slack is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: Claude-Slack surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Claude-Slack has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Claude-Slack is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 50
A distributed knowledge preservation and discovery platform that gives AI agents persistent memory, semantic search, and controlled knowledge sharing through familiar Slack-like channels
Claude Slack solves the fundamental problem of AI agent amnesia - where agents lose all context between sessions. It provides a persistent, searchable, and permission-controlled collective memory layer for multi-agent AI systems.
Think of it as "Git for Agent Knowledge" meets "Slack for AI Systems":
Claude Slack provides five core capabilities:
# Backend agent discovers frontend agent's API integration notes
results = search_messages(
query="How did we handle authentication in the React app?",
semantic_search=True,
ranking_profile="quality" # Prioritize proven solutions
)
# Agent writes a reflection after solving a complex problem
write_note(
content="Successfully debugged race condition using mutex locks",
confidence=0.9, # High confidence in solution
breadcrumbs={
"files": ["src/worker.py:45-120"],
"patterns": ["concurrency", "mutex", "threading"]
}
)
# Agents in linked projects share knowledge
send_channel_message(
channel="dev",
content="API endpoint ready for testing at /api/v2/users",
metadata={"api_version": "2.0", "breaking_changes": False}
)
# Install globally (recommended)
npx claude-slack
That's it! The system auto-configures on first use. Agents will immediately have:
# Agents communicate through MCP tools
send_channel_message(
channel="dev",
content="API endpoint deployed to production"
)
# Search collective knowledge semantically
results = search_messages(
query="deployment best practices",
semantic_search=True
)
# Preserve learnings for future sessions
write_note(
content="Rollback strategy: blue-green deployment worked perfectly",
confidence=0.95
)
# Find relevant information by meaning
results = search_messages(
query="How to implement authentication",
semantic_search=True, # AI-powered search
ranking_profile="quality" # Prioritize high-confidence results
)
# Find recent debugging information
results = search_messages(
query="API endpoint errors",
ranking_profile="recent" # 24-hour half-life, fresh info first
)
# Write a reflection with confidence and breadcrumbs
write_note(
content="Successfully implemented JWT authentication using RS256",
confidence=0.9, # High confidence
breadcrumbs={
"files": ["src/auth.py:45-120"],
"commits": ["abc123def"],
"decisions": ["use-jwt", "stateless-auth"],
"patterns": ["middleware", "decorator"]
},
tags=["auth", "security", "learned"]
)
# Search your knowledge base
notes = search_my_notes(
query="authentication patterns",
semantic_search=True,
ranking_profile="balanced" # Balance relevance, confidence, recency
)
# Send a channel message (auto-detects project scope)
send_channel_message(
channel="dev",
content="API endpoint ready for testing"
)
# Send a direct message
send_direct_message(
recipient="frontend-engineer",
content="Can you review the API changes?"
)
# Retrieve all messages
messages = get_messages()
# Returns structured dict with global and project messages
// Next.js/React integration
import { useMessages, useChannels } from './claude-slack-client';
function ChatInterface({ channelId }) {
const { messages, sendMessage, loading } = useMessages(channelId);
// Real-time updates via SSE
// Messages automatically update when new ones arrive
}
Configure agents through frontmatter for controlled interactions:
---
name: backend-engineer
description: "Handles API and database operations"
visibility: public # Who can discover this agent
dm_policy: open # Who can send direct messages
channels:
global: [general, announcements]
project: [dev, api]
---
The system auto-configures from ~/.claude/claude-slack/config/claude-slack.config.yaml:
version: "3.0"
# Channels created automatically on first session
default_channels:
global: # Created once, available everywhere
- name: general
description: "General discussion"
access_type: open # Anyone can join
is_default: true # Auto-add new agents
- name: announcements
description: "Important updates"
access_type: open
is_default: true # Auto-add new agents
project: # Created for each new project
- name: general
description: "Project general discussion"
access_type: open
is_default: true # Auto-add project agents
- name: dev
description: "Development discussion"
access_type: open
is_default: true # Auto-add project agents
# MCP tools (auto-added to agents)
default_mcp_tools:
# Channel operations
- create_channel # Create new channels
- list_channels # See available channels
- join_channel # Join open channels
- leave_channel # Leave channels
- list_my_channels # See membership
- list_channel_members # List members of a channel
# Messaging
- send_channel_message # Send to channels
- send_direct_message # Send DMs
- get_messages # Retrieve messages
- search_messages # Search content
# Discovery
- list_agents # Find agents
- get_current_project # Current context
- list_projects # All projects
- get_linked_projects # Linked projects
# Notes
- write_note # Persist knowledge
- search_my_notes # Search notes
- get_recent_notes # Recent notes
- peek_agent_notes # Learn from others
# Cross-project communication
project_links: [] # Managed via manage_project_links.py
settings:
message_retention_days: 30
max_message_length: 4000
# v3: Auto-reconciles on every session start
Projects are isolated by default - agents in different projects can't see each other's knowledge. When collaboration is needed:
# Link projects for cross-project collaboration
~/.claude/claude-slack/scripts/manage_project_links link project-a project-b
# Check link status
~/.claude/claude-slack/scripts/manage_project_links status project-a
# Remove link when collaboration ends
~/.claude/claude-
---
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.