"A system for identifying objects" matching MCP servers:

Enables persistent, auditable business operations state by storing knowledge, evidence, decisions, tasks, execution receipts, and review results in a local SQLite database, so different sessions can continue the same project.

Provides AI assistants with a standardized interface to interact with the Todo for AI task management system. It enables users to retrieve project tasks, create new entries, and submit completion feedback through natural language.

Enables coding agents to query the dependency graph of a GitHub backlog, retrieve ordered ready work and prerequisite chains, atomically claim issues, and report blockers—so agents work in the correct order and safely in parallel.

Comprehensive quest orchestration system with KĀDI broker integration, multi-channel approval workflow, and Git-backed data storage.

Provides MCP access to an internal performance and consulting project collaboration system, enabling management of projects, stages, tasks, materials, evidence, approvals, and experience in a traceable chain, with Feishu for organization sync and collaboration.

Enables creating Jira issues and listing issue types for a Jira Cloud project using Basic Auth credentials.

A deterministic MCP server that reimplements ai-git-fish workflows (aicommit, aibranch, aipr) with Leantime integration, enabling Claude Code and Codex to perform git operations and manage tickets without an internal LLM.

Submit and inspect governed business-system actions through a BailingHub control plane, with tools for submitting, retrieving, and waiting on governed jobs.

Enables Claude to interact with System Task projects, teams, and tasks, providing daily briefs, project reports, team load, and risk identification, as well as creating and updating tasks and demands.

Exposes a Notion-synced AI OS as read-only MCP tools, enabling MCP-compatible AI clients to search the vault, fetch page contents, list projects, and check project statuses without scraping public links.

A shared coordination layer for multiple AI coding assistants, exposing a persistent task queue, per-task message threads, and progress tracking via JSON files on disk.

A persistent state machine and notification system for AI agents to manage complex, multi-step workflows via the Model Context Protocol, preventing context drift by maintaining structured checklists and sending desktop alerts.

Manages continuation notes for projects, enabling session handoff and historical browsing through a two-location storage system.

Enables construction permitting teams to analyze portfolios of active permits by ranking risk, detecting day-over-day changes, identifying systemic bottlenecks, and generating daily executive action plans. Also supports single-permit readiness audits, missing-document reports, blocker explanations, resubmission checklists, and semantic search over municipal requirements.

Enables AI agents to read-only inspect an OmniFocus database, retrieving exact tasks and projects, Inbox roots, complete project hierarchies, tags, dates, notes and workload or review overviews. All access is read-only and bounded, with no mutation, write tools or sync triggers.

Connects Claude to Jobber to manage clients, jobs, invoices, quotes, and scheduling through natural language.

A Model Context Protocol server enabling AI assistants to interact with Tempo's time tracking system in JIRA for worklog retrieval, creation, and management.

Enables multiple AI agents and humans working in the same project to share status, exchange messages, and claim files through a local collaboration board. It supports project-specific enablement, conflict-aware file claims, and shared state via SQLite.

Read-only MCP server for the HIT ticket management system that lists queues, searches/fetches ticket details, and lists ticket templates.

MCP server for AL Object ID management in Microsoft Dynamics 365 Business Central development. It provides intelligent object ID allocation, collision prevention, and team collaboration features.