comms-mcp
CLAUDE.md1 starsChanged 12 days agoMITView on GitHub
Unified fleet comms gateway (Telegram / WhatsApp / Slack / Teams) behind the comms_ops portmanteau. Allowlist-gated send, sanitized inbound, 7-day retention, SQLite outbox. Backend :11205, console :11204, wa-sidecar :11208. - uv run python -m comms_mcp — stdio; MCP_PORT=11205 → HTTP daemon - just serve | test | lint | fix | fmt | types | ci | bootstrap | mcpb-pack - Console: web_sota/ (bun run dev, proxied to :11205 in dev, served from :11205 root via web_sota/dist in daemon mode)…
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- llms-full.txtllms.txt
- llms.txtllms.txt
- commsSkill
- commsSkill
The file
Files
CLAUDE.md — comms-mcp
Unified fleet comms gateway (Telegram / WhatsApp / Slack / Teams) behind the
comms_ops portmanteau. Allowlist-gated send, sanitized inbound, 7-day
retention, SQLite outbox. Backend :11205, console :11204, wa-sidecar :11208.
Entry points
uv run python -m comms_mcp— stdio;MCP_PORT=11205→ HTTP daemonjust serve | test | lint | fix | fmt | types | ci | bootstrap | mcpb-pack- Console:
web_sota/(bun run dev, proxied to :11205 in dev, served from:11205root viaweb_sota/distin daemon mode) - NSSM:
scripts/install-services.ps1(elevated) —comms-mcp+comms-mcp-wa
Standards that bite here
TOOL_DESIGN_STANDARDS.md§4.2 dialogic returns (success+message), §7.1 error handling (_error_response+logger.exception), §9 MCP annotation hints — not custom keys.STARLETTE_NO_PYDANTIC_STANDARD.md— the/mcpmount pattern (http_app(path="/")+mount("/mcp"), bare-path rewrite middleware, composedmcp_http.lifespan(app)); verify with a realfastmcp.Client("http://127.0.0.1:PORT/mcp"), never in-process ASGI.- Fleet ruff:
T20(noprintin server code) enforced; per-file-ignores for CLI/build/test paths only.
Key files
src/comms_mcp/server.py— FastAPI +/mcpmount + RESTsrc/comms_mcp/__main__.py— dual transport + stdio→daemon probe/proxysrc/comms_mcp/mcp/tools/comms.py— the portmanteau;admin.py— shutdownsrc/comms_mcp/adapters/*.py— one module per channel (allowlist + sanitize)src/comms_mcp/outbox/sqlite.py— outbox + inbound store, TTL purgeskills/comms/SKILL.md— agent domain skill (alsoGET /api/skills)docs/ONBOARDING.md— per-channel setup;docs/TROUBLESHOOTING.md— fixes
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

