"Wear OS" matching MCP servers:

Read-only MCP server that exposes the agentic-os governance, SDLC, and Quality Engineering methodology to any MCP host. It never writes to your repository and never executes code — it serves the methodology, plans an install, and verifies it, handing any commands back to the host to run.

Stops AI agents reopening rejected decisions and forgetting project state. Persistent operational state for agents: decisions, plans, blockers, priorities and patterns that survive across sessions, with enforcement. Not conversation logs.

Enables code agents to persist and recall durable project knowledge — rules, decisions, procedures, learnings and secrets — across sessions at low context cost, with accent-insensitive PT-BR search, scoped per repository/workspace, and secrets that stay out of the model's context.

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.

Enables AI coding agents to fetch live MDN Web Docs pages, TypeScript handbook content, and npm package metadata as clean markdown, with local search, caching, and polite throttling.

Trust Ledger OS MCP server exposing tools to inspect phases, routes, packages, and the project manifest.

Bridges Design OS exported component packages into target projects, handling migrations across different CSS, component, and icon libraries.

Enables checking project files like Dockerfile, .nvmrc, and CI workflows to determine whether pinned runtime, database, and OS versions are still supported, providing end-of-life dates, latest patches, and upgrade targets for 470+ products.

Enables AI coding agents to reverse engineer an operating system from its ISO and rebuild it component by component, exposing 39 tools over stdio for ISO fingerprinting, sandboxed QEMU VM lifecycle, PE analysis, API-surface dumps, syscall tracing, behavior diffs, component scaffolding, compat shims, app-compat testing, and knowledge-base search. It lets an agent survey a reference OS, generate clean-room specs and code, boot the rebuild, and test real applications against it.

MCP bridge server for patchwork-os. Boots a stdio-HTTP bridge with MCP introspection over /mcp, supporting tools/list and the full MCP protocol over HTTP.

MCP server for coding-os, a cognitive operating system that gives AI agents memory, structure, and discipline. It exposes tools for project management, task tracking, knowledge graphs, and cognition traces to Claude Code and Codex.

A zero-data MCP server for LLM fine-tuning, providing 64 tools across 10 dimensions to prepare, build, train, evaluate, secure, package, and deliver fine-tuned models without ever accessing client data.

Enables workflow management and Docker image building for Bio-OS platform. Supports WDL workflow submission, validation, and monitoring, along with Docker image building and status tracking for bioinformatics workflows.

Enforces engineering governance for AI-driven software projects, ensuring state over prompt, freeze over generate, and audit over output through the 5S workflow.

Enables game gun models to be given physically based surface finishes across material slots and wear levels, with wear baked once into vertex-colour masks for edges, handling, rubbing parts and dirt. It also validates finishes and wear against physical rules, renders look-dev variant sheets, and exports per-slot engine material parameters.

An LLM-native decision tracking system that captures unexpected engineering outcomes as 'pressure events' to build a persistent learning foundation. It enables AI assistants to manage cases, log surprises, and promote recurring insights into global or project-specific knowledge bases.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

A ready-to-deploy MCP server with in-process agent verification via KYA-OS Checkpoint, enabling secure tool access for verified agents.

Enables Codex to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events backed by a matching project-record Git commit. Access is scoped to one workspace and project via short-lived, revocable, hash-stored credentials that cannot reach members, keys, deletion, publication, or deployment.

Enables Codex agents to read a project's kickoff card, acceptance criteria, progress, Git trail, and handoff package, then append one validated, idempotent progress event with an agent verification note and matching Git commit. Access is limited to short-lived, scoped, revocable credentials bound to a single workspace and project, with high-risk actions kept outside the tool surface.