obo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| obo_createB | Create a new OBO session file and update index.json atomically. Args: base_dir: Project root directory (session goes in {base_dir}/.github/obo_sessions/) title: Human-readable session title description: What this session is reviewing items: List of item dicts (title, description, urgency, importance, effort, dependencies, category are all optional with defaults) session_filename: Optional explicit filename (e.g. session_20260314_120000.json). If omitted, generated from current timestamp. |
| obo_list_sessionsA | List OBO sessions from index.json. Args: base_dir: Project root directory status_filter: Optional filter — 'active', 'completed', or 'incomplete' (incomplete = active sessions with pending items) |
| obo_session_statusA | Return summary statistics for an OBO session. Args: session_file: Absolute path or filename relative to {base_dir}/.github/obo_sessions/ base_dir: Required if session_file is a bare filename |
| obo_nextA | Return the next item to work on. Returns in_progress items first (highest priority_score), then pending. Args: session_file: Absolute path or filename relative to {base_dir}/.github/obo_sessions/ base_dir: Required if session_file is a bare filename |
| obo_list_itemsA | List all items in a session, sorted by priority_score descending. Args: session_file: Absolute path or filename relative to {base_dir}/.github/obo_sessions/ base_dir: Required if session_file is a bare filename status_filter: Optional — 'pending', 'in_progress', 'completed', 'skipped' |
| obo_get_itemB | Return full detail for a single item. Args: session_file: Absolute path or filename relative to {base_dir}/.github/obo_sessions/ item_id: Item ID (integer or string) base_dir: Required if session_file is a bare filename |
| obo_mark_completeA | Mark an item as completed with resolution text. Args: session_file: Absolute path or filename relative to {base_dir}/.github/obo_sessions/ item_id: Item ID to mark complete resolution: Text describing how the item was resolved base_dir: Required if session_file is a bare filename |
| obo_mark_skipA | Mark an item as skipped. Args: session_file: Absolute path or filename relative to {base_dir}/.github/obo_sessions/ item_id: Item ID to skip base_dir: Required if session_file is a bare filename reason: Optional reason for skipping |
| obo_update_fieldA | Update any field on an item. Auto-recalculates priority_score when a score component (urgency, importance, effort, dependencies) is changed. Args: session_file: Absolute path or filename relative to {base_dir}/.github/obo_sessions/ item_id: Item ID to update field: Field name (e.g. 'urgency', 'title', 'description', 'status') value: New value (always passed as string; numeric fields are cast automatically) base_dir: Required if session_file is a bare filename |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose with no ambiguity: create sessions, get/list items, list sessions, mark items complete/skip, find next item, get session status, and update item fields. The operations target specific resources and actions without overlap.
All tools follow a consistent 'obo_verb' or 'obo_verb_noun' pattern (e.g., obo_create, obo_get_item, obo_list_sessions). The naming is uniform throughout, using snake_case and clear action descriptors.
With 9 tools, the server is well-scoped for managing OBO sessions and items. Each tool serves a distinct function in the workflow, from creation to status tracking, without being excessive or insufficient for the domain.
The toolset provides complete CRUD/lifecycle coverage for OBO sessions and items: create sessions, list/get/update items, mark items as complete/skip, track status, and find next tasks. No obvious gaps exist for the stated purpose of session management.