Ai Agent Mcp Server — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Ai Agent Mcp Server (MCP Server) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A Model Context Protocol (MCP) server that enables real-time communication between multiple AI agents. Designed for orchestrating teams of specialized AI agents (frontend, backend, tester, DevOps, etc.) working on shared projects.
Uses Redis for data storage and pub/sub messaging, enabling multi-instance deployments with real-time capabilities.
Includes a real-time web dashboard for full transparency into agent communications, workloads, tasks, and shared artifacts.
git clone https://github.com/your-username/ClaudeAgentMCPServer
cd ClaudeAgentMCPServer
npm install
npm run buildOption A: Docker (recommended)
docker compose up -d
# → Redis at localhost:6379
# → Dashboard at http://localhost:3456Option B: Without Docker
# Install Redis manually:
# macOS: brew install redis && brew services start redis
# Ubuntu: sudo apt install redis-server && sudo systemctl start redis
# Windows: https://github.com/microsoftarchive/redis/releases
# Start the dashboard separately
cd dashboard
npm install
npm start
# → Dashboard at http://localhost:3456Then wire Claude to the MCP server (see Connecting Claude below).
Why is the MCP server not in Docker? The MCP server communicates over stdio — Claude launches it directly as a child process. It is not an HTTP service and cannot be reached via a network port. Docker handles Redis (shared state) and the dashboard (monitoring UI) only.
A .mcp.json is included in this repo. When you open this folder in Claude Code it will prompt you to enable the agent-team MCP server automatically. Redis must be running first (docker compose up -d).
Edit your Claude Desktop config file:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
Add this block (replace the path with your actual clone location):
{
"mcpServers": {
"agent-team": {
"command": "node",
"args": ["/absolute/path/to/ClaudeAgentMCPServer/dist/index.js"],
"env": {
"REDIS_HOST": "localhost",
"REDIS_PORT": "6379"
}
}
}
}Restart Claude Desktop after saving.
| Variable | Default | Description |
|---|---|---|
REDIS_HOST | localhost | Redis server host |
REDIS_PORT | 6379 | Redis server port |
REDIS_PASSWORD | (none) | Redis password if required |
REDIS_DB | 0 | Redis database number |
REDIS_PREFIX | agent-team: | Key prefix for all Redis keys |
DASHBOARD_PORT | 3456 | Web dashboard port |
agent_register - Register an agent with the teamagent_heartbeat - Send heartbeat to maintain presenceagent_deregister - Leave the teamteam_status - Get status of all team membersagent_status - Get detailed status of specific agentlist_agents - List all agents with optional filterssend_message - Send direct message to another agentget_messages - Get inbox or sent messagesbroadcast_message - Broadcast to all agents or a role groupget_unread_count - Get unread message countchannel_subscribe - Subscribe to a topic channelchannel_unsubscribe - Unsubscribe from a channelchannel_publish - Publish message to a channelchannel_history - Get recent channel messageslist_channels - List all available channelstask_create - Create a new tasktask_update - Update task status, assignee, add notestask_get - Get task detailstask_list - List tasks with filterstask_history - Get task event historyartifact_register - Register a shared artifactartifact_list - List artifacts with filtersartifact_get - Get artifact detailsartifact_notify - Notify agents about artifact changesartifact_search - Search artifacts by path patternThe dashboard server exposes the following REST endpoints:
GET /api/team-status - Get all agents and their current statusGET /api/tasks - Get all tasks with summary by statusGET /api/messages/recent - Get 50 most recent messagesGET /api/communication-graph - Get communication patterns (who talks to whom)GET /api/agent-workload - Get per-agent workload and task breakdownGET /api/message-chains - Get threaded message conversationsGET /api/artifacts - Get all shared artifacts with full contentGET /api/activity - Get activity feed with all team eventsDashboard connects to server via WebSocket (ws://localhost:3456) for real-time updates:
agent_register({
agentId: "frontend-1",
role: "frontend-engineer",
name: "Frontend Agent 1",
capabilities: ["react", "typescript", "tailwind"]
})team_status()send_message({
from: "frontend-1",
to: "backend-1",
type: "request",
subject: "Need User API",
content: "Please create GET /api/users/{id} endpoint. Need: id, name, email, avatar",
priority: "high"
})task_create({
title: "Implement User Profile API",
description: "Create REST endpoint for user profile data",
priority: "high",
assignee: "backend-1",
reporter: "frontend-1"
})channel_publish({
agentId: "backend-1",
channel: "api-updates",
content: "User API v1.0 deployed. GET /api/users/{id} now available."
})Open http://localhost:3456 in your browser to see:
All dashboard sections update in real-time as agents communicate and work progresses.
Click any message in "Recent Messages" to open a detailed modal showing:
Click any artifact card in "Shared Artifacts" to open a detailed modal showing:
| Agent ID | Role | Responsibilities |
|---|---|---|
| lead-agent | Team Lead | Task coordination, architecture |
| frontend-1, frontend-2 | Frontend Engineer | React/Next.js, UI/UX |
| backend-1, backend-2 | Backend Engineer | API, business logic |
| devops-1 | DevOps Engineer | CI/CD, deployment |
| tester-1, tester-2 | QA Engineer | Testing |
| security-1 | Security Engineer | Security audits |
| docs-1 | Documentation | API docs, guides |
| db-1 | Database Admin | Schema, optimization |
| api-1 | API Designer | OpenAPI specs |
| ui-1 | UI/UX Designer | Design system |
| perf-1 | Performance Engineer | Optimization |
| infra-1 | Infrastructure | AWS, scaling |
# Run in development mode
npm run dev
# Build
npm run build
# Start built version
npm startnode dashboard/test-data.js to populate test dataredis-cli ping should return PONGredis.type()REDIS_HOST and REDIS_PORT match in MCP server and dashboardDASHBOARD_PORT=3457 npm start to use different portlsof -i :3456 (macOS/Linux) or netstat -an | findstr :3456 (Windows)src/index.ts): Handles agent communication, tasks, artifactsdashboard/server.js): Express server + WebSocket for real-time updatesdashboard/public/index.html): Vue-like reactive UIAgents (Claude Code clients)
↓
MCP Server ← → Redis ← → Dashboard Server ← WebSocket ← Dashboard UIagents:registry (hash): All registered agentstasks:all (set): Task IDs, tasks:{id} (string): Task datamessages:inbox:{agentId} (list): Messages for agentartifacts:all (set): Artifact IDs, artifacts:{id} (string): Artifact data{type}:channels:{name} (list): Channel messagesMIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.