Sos

database MCP Server

MCP-native AI agent OS — Redis bus, squad service, multi-model engine. Connect any agent with one URL.

Verified
databasedatabaseredis
3 views2 stars0 forks

Why This Matters

Discovered via github-topic:mcp and last synced 3mo ago.

Verified
Source
github-topic:mcp
Stars
2
Last synced
3mo ago
Install
Check source

Install

Install instructions not detected yet

Check the source repository for the latest setup steps.

View source instructions
30
Tools
0
Resources
0
Prompts
Standard I/O
Transport

Available Tools (30)

No

No

inbox

Read your incoming messages

task_list

List tasks for a squad or agent

Gateway

6062

Feature

SOS

search_code

Semantic search across the codebase

Squad

8060

Basic

No

recall

Retrieve from Mirror memory by query

broadcast

Send a message to all connected agents

status

Check system health

aviation

Claude Opus, GPT-5

ask

Send a message and wait for a reply

onboard

Provision a new agent or project

diesel

Gemma 4 31B (free), Claude Haiku

AutoGen

LangGraph

Cloud-first

The core difference: **the bus IS MCP SSE**. Not a wrapper. Not an adapter added in v2. Every tool call, every agent message, every task update flows through the same MCP transport Claude Code already speaks. --- ## Docs - [Agent Wiring — Claude Code + Codex + SOS](docs/architecture/AGENT_WIRING.md) — Mermaid diagrams, sequence flows, transport comparison, quick connect reference ## Architecture ``` Claude Code / Cursor / any MCP client │ │ SSE (one URL) ▼ ┌─────────────────────────────────────────────┐ │ SOS MCP Server (:6070) │ │ 12 tools: send · inbox · peers · ask │ │ remember · recall · search_code │ │ task_create · task_list · task_update │ │ onboard · broadcast · status │ └──────────┬──────────────────────────────────┘ │ ┌────────▼────────┐ │ Redis Bus │ ← streams, pub/sub, wake-on-message └────┬──────┬─────┘ │ │ ┌─────▼──┐ ┌─▼──────────┐ ┌────────────┐ │ Squad │ │ Engine │ │ Mirror │ │ :8060 │ │ :6060 │ │ :8844 │ │ tasks │ │ model route│ │ memory │ │ skills │ │ failover │ │ pgvector │ └────────┘ └────────────┘ └────────────┘ ``` Agents are not processes SOS manages. They are external — Claude Code sessions, Python scripts, whatever. They connect to the MCP SSE endpoint, get 12 tools, and can talk to each other, create tasks, read memory, and route work. --- ## Quick Start **Prerequisites:** Python 3.11+, Redis, git ```bash # 1. Clone git clone https://github.com/Mumega-com/sos.git cd sos # 2. Install pip install -e . # 3. Configure cp .env.example .env # Edit .env: add REDIS_URL, ANTHROPIC_API_KEY, GEMINI_API_KEY, etc. cp sos/bus/tokens.json.example sos/bus/tokens.json # Edit tokens.json: add your agent tokens # 4. Start core services python3 -m sos.services.engine # model engine :6060 python3 -m sos.services.squad # squad + tasks :8060 python3 -m sos.mcp.sos_mcp_sse # MCP SSE server :6070 # Or use systemd (see systemd/ directory for unit files) ``` **Connect Claude Code (or any MCP client):** ```json { "mcpServers": { "sos": { "url": "https://your-server.com/sse/YOUR_TOKEN" } } } ``` That's it. Your agent now has 12 tools to communicate, manage tasks, and access shared memory. --- ## MCP Tools All 12 tools are available the moment an agent connects.

memories

List recent memories

Yes

Needs more

Service

Port

peers

See which agents are online

task_update

Update task status or result

Tier

Models

send

Send a message to another agent by name

task_create

Create a task in the squad service

Mirror

8844

6070

SSE endpoint — agents connect here

Manual

Manual

remember

Store something in shared Mirror memory

Engine

6060

Works Well With - Skills

implementing-api-rate-limiting-and-throttling

Implements API rate limiting and throttling controls using token bucket, sliding window, and fixed window algorithms to protect against brute force attacks, credential stuffing, resource exhaustion, and API abuse. The engineer configures per-user, per-IP, and per-endpoint rate limits using Redis-backed counters, API gateway plugins, or application middleware, and implements proper HTTP 429 responses with Retry-After headers. Activates for requests involving rate limiting implementation, API throttling setup, request quota management, or API abuse prevention.

61 starsHas guide

database-engineering

Use this skill when designing database schemas, optimizing queries, creating indexes, planning migrations, or choosing between database technologies. Triggers on schema design, normalization, indexing strategies, query optimization, EXPLAIN plans, migrations, partitioning, replication, connection pooling, and any task requiring database architecture or performance decisions.

2 starsHas guide

database-v2

Database Workflow Bundle workflow skill. Use this skill when the user needs Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

1 starsHas guide

appdeploy-v2

AppDeploy Skill workflow skill. Use this skill when the user needs Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

1 starsHas guide