MCP server for durable one-by-one review workflows, with prioritized session state for coding agents.
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":"oboe-mcp","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.
<!-- Copyright (C) 2026 Gregory R. Warnes SPDX-License-Identifier: AGPL-3.0-or-later This file is part of Oboe MCP. For commercial licensing, contact greg@warnes-innovations.com --> # Oboe MCP Structured one-by-one workflows for coding agents. MCP server for durable one-by-one review workflows, with prioritized session state for coding agents. Provides 20 tools for creating, navigating, and resolving items in priority-scored session files, including blocked-item handling, first-class approval updates, and nested child sessions. Licensed under `AGPL-3.0-or-later` with commercial licensing available. See `LICENSE` for full terms. ## PyPI Package Install or run Oboe MCP directly from PyPI using either of these alternatives: - Run it without installing: `uvx oboe-mcp` - Install it into your current environment: `pip install oboe-mcp` Installing `oboe-mcp` also installs the `oboe-cli` command: ```bash # After pip install oboe-mcp oboe-cli --help # From PyPI uvx --from oboe-mcp oboe-cli --help # From a local checkout (no install needed) uvx --from /path/to/oboe-mcp oboe-cli --help ``` ## CLI Reference (`oboe-cli`) Installing `oboe-mcp` also installs `oboe-cli`, a human-friendly command-line companion for the same session files the MCP tools operate on. ```bash oboe-cli [--session SESSION] [--base-dir DIR] COMMAND [ARGS...] ``` Global options: | Option | Description | | ------ | ----------- | | `--session SESSION`, `-s` | Session filename (e.g. `session_20260411_120000.json`) or absolute path | | `--base-dir DIR`, `-b` | Project root containing `.github/oboe_sessions/` (defaults to CWD detection) | **Base-dir auto-detection**: when `--base-dir` is omitted, `oboe-cli` uses the current working directory if it contains a `.github/oboe_sessions/` folder, otherwise it falls back to the working directory as-is. ### Commands | Command | Description | | ------- | ----------- | | `sessions` | List all sessions (supports `--status active\|paused\|completed\|in…
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.