MCP server for multi-session awareness and coordination
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-session-registry","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-session-registry [](https://github.com/filhocf/mcp-session-registry/actions/workflows/ci.yml) [](https://www.python.org/downloads/) [](LICENSE) Lightweight MCP server for multi-session awareness — lets AI agents know who else is active on the same machine. ## Why When you run multiple AI CLI sessions (Kiro, Claude Code, Gemini CLI) on the same machine, they are blind to each other. This causes: - **File conflicts** — two sessions editing the same file - **Duplicated work** — agents picking up the same task - **Wasted context** — no way to know what another session is doing **mcp-session-registry** solves this with a shared presence layer: - Sessions register on spawn, declare a theme, and heartbeat every 2-3 minutes - Sessions claim files/resources — other sessions see the claim before touching them - Stale sessions (no heartbeat >5min) are automatically reaped - Everything persists in SQLite — survives individual session crashes ## Quick Start ```bash # Run directly uvx mcp-session-registry # Or install pip install mcp-session-registry # Configure port (default: 8000) MSR_PORT=3203 mcp-session-registry ``` ## MCP Tools | Tool | Description | |------|-------------| | `session_register` | Register a new session. Returns `session_id` for subsequent calls. | | `session_list` | List all active sessions on this machine. | | `session_heartbeat` | Send heartbeat to keep session alive (call every 2-3 min). | | `session_end` | Gracefully end a session and release all its claims. | | `session_claim` | Claim a resource (file, branch, work item). Advisory lock. | | `session_release` | Release a previously claimed resource. | | `session_conflicts` | Check if resources are claimed by another active session. | ## How It Works `…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.