Perseus for Slack — Live Context for Developer Teams
Perseus brings live project context into Slack via MCP — answering "what's running?", "what did we decide?", and "where's that code?" so developer teams ship faster without leaving chat.
Built for the Slack Agent Builder Challenge 2026 (New Slack Agent track) using Perseus MCP server integration.
What it does
@perseus services— check service health from Slack@perseus memory <topic>— recall team decisions and context@perseus search <query>— find code across the project@perseus onboard— new team member context dump@perseus ask <question>— natural language project queries
Architecture
Slack User → Slack Agent (Bolt) → MCP → Perseus Server
├── perseus_services (health)
├── perseus_memory (Mimir recall)
├── perseus_read (file inspection)
├── perseus_list ─┐ code search:
│ ├─ enumerate + grep
├── perseus_read ─┘ (client-side)
└── perseus_get_context (NL context)
Why MCP
The Slack challenge requires MCP server integration, Slack AI, or Real-Time Search. Perseus ships as a production MCP server with 27+ tools for context resolution — we're wiring real infrastructure into Slack, not building a toy.
Quickstart
pip install -r requirements.txt
cp .env.example .env # fill in SLACK_BOT_TOKEN, PERSEUS_MCP_URL
python src/app.py
Project structure
├── src/ # Slack Bolt agent (Python)
│ ├── app.py # Main app, mentions + slash commands
│ ├── mcp_client.py # MCP client (Perseus server)
│ ├── handlers.py # Intent routing
│ └── blocks.py # Slack Block Kit formatters
├── demo/ # Demo video script + transcript
├── docs/ # Architecture docs + submission
└── assets/ # Architecture diagram
Hackathon
- Challenge: Slack Agent Builder Challenge
- Track: New Slack Agent (MCP server integration)
- Deadline: July 13, 2026
- Prize: $42,000 + Dreamforce trip
License
MIT — LICENSE
