Perseus for Slack
Provides live project context within Slack, enabling developer teams to check service health, manage checkpoints, recall team decisions, search code, and receive AI-powered task suggestions, all through natural language commands and MCP integration.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Perseus for Slackcheck service health"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 health— workspace health report (stale checkpoints, duplicate work)@perseus checkpoint <task>/@perseus recover— save session state, let anyone on the team pick it up@perseus suggest [task]— AI task recommendation via Pythia (local LLM optional, honestly labeled)@perseus session [N]— recent session digests@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
Related MCP server: graqle
Architecture
Dual transport: read-only queries go over MCP; state-changing verbs and the Pythia suggestion engine go through the Perseus CLI.
Slack User → Slack Agent (Bolt) ─┬─ MCP (JSON-RPC 2.0 / HTTP) → Perseus MCP server
│ ├── perseus_services (health)
│ ├── perseus_get_health (drift, stale/dupe checkpoints)
│ ├── perseus_memory (Perseus Vault recall)
│ ├── perseus_session (session digests)
│ ├── perseus_read (file inspection)
│ ├── perseus_list ─┐ code search:
│ ├── perseus_read ─┘ enumerate + grep (client-side)
│ └── ... 31 tools, auto-generated from the directive registry
└─ CLI subprocess → perseus checkpoint / recover / suggest
└── suggest --llm → any OpenAI-compatible endpoint (optional)Why MCP
The Slack challenge requires MCP server integration, Slack AI, or Real-Time Search. Perseus ships as a production MCP server whose directive registry auto-generates 31 tools (measured via tools/list) with zero per-tool schema wiring — we're wiring real infrastructure into Slack, not building a toy.
AI suggestions — no GPU required
@perseus suggest runs Pythia, the Perseus tool oracle. Two modes, always labeled in the Slack response so nobody mistakes one for the other:
Mode | When | What you see |
⚡ Live LLM |
| Model's recommendation + provider/model footer |
📊 Deterministic | no LLM configured | Keyword-ranked top skills + "no LLM configured" footer |
Any OpenAI-compatible endpoint works — all CPU-friendly options:
# Ollama (easiest): ollama pull llama3.2:3b
PERSEUS_LLM_PROVIDER=ollama PERSEUS_LLM_MODEL=llama3.2:3b PERSEUS_LLM_URL=http://localhost:11434
# llama.cpp / LM Studio / Lemonade / vLLM — anything serving /v1/chat/completions
PERSEUS_LLM_PROVIDER=openai-compat PERSEUS_LLM_MODEL=<model-id> PERSEUS_LLM_URL=http://localhost:1234Quickstart
pip install -r requirements.txt
pip install perseus-ctx # Perseus MCP server + CLI
# 1. Start the Perseus MCP server from your project directory
perseus mcp serve --transport sse --port 8420 # set mcp.sse_bearer_token in config.yaml
# 2. Run the Slack agent
cp .env.example .env # fill in SLACK_BOT_TOKEN, SLACK_APP_TOKEN, PERSEUS_MCP_TOKEN
python src/app.pyProject 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 diagramHackathon
Challenge: Slack Agent Builder Challenge
Track: New Slack Agent (MCP server integration)
Deadline: July 13, 2026
Prize: $42,000 + Dreamforce trip
License
MIT — LICENSE
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityFmaintenanceEnables bidirectional communication between MCP clients and Slack, allowing users to receive task notifications and respond to AI inquiries directly within Slack threads. It supports various urgency levels, message threading, and interactive question-and-answer workflows.Last updated3MIT
- Alicense-qualityBmaintenanceDev intelligence layer that builds a knowledge graph from any codebase and exposes 7 MCP tools for graph-powered reasoning, impact analysis, and preflight safety and governance checks.Last updated32Apache 2.0
- AlicenseAqualityDmaintenanceA unified developer toolkit for AI-assisted workflows. Task timing, doc drift detection, env validation, secret scanning, port conflict resolution, AI context generation, and license auditing — one MCP server, one install.Last updated73MIT
- Alicense-qualityBmaintenanceA production-ready MCP server for the Slack API that enables searching, listing channels, reading history, inspecting users, fetching threads, and sending messages through controlled Slack tools.Last updated24,128MIT
Related MCP Connectors
Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
One shared context your team's AI tools read & write over MCP. No re-explaining. Free.
A MCP server built for developers enabling Git based project management with project and personal…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Perseus-Computing-LLC/slack-perseus-agent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server