Shawn Core MCP
Shawn Core MCP
Shawn Core MCP es un servidor MCP JSON-RPC local-first para el enrutamiento práctico de especialistas, la continuidad y los traspasos basados en evidencia.
El orquestador público se llama Orchestrator. Mantiene un mapa conciso de cada especialista para tareas ordinarias y solo escala cuando se necesita una prueba más profunda. Eso mantiene el enrutamiento útil sin convertir cada pequeña solicitud en una ceremonia multiagente.
Cada especialista público tiene la misma línea base de contrato 8/10: recepción, evidencia, traspaso y límite público. Esto mide la completitud operativa pública, no una afirmación de que cada dominio tenga la misma profundidad técnica.
Herramientas principales incluidas
orchestrator_route: devuelve el primer especialista y el plan de validación.token_master_audit: inventaría los datos de configuración local relevantes para tokens.changelog_intake: inicia un plan ligero de subproceso de changelog con un traspaso de Atlas Cartographer, una instantánea local de Git y un traspaso de@github.changelog_finalize: crea una entrada de changelog respaldada por un recibo al final de la tarea.atlas_continuity_record: escribe una tarjeta compacta de Cartographer sin carga útil bajo una raíz de continuidad local seleccionada por el operador.personal_git_snapshot: lee el estado y el último commit de un repositorio local de Git en la lista de permitidos.personal_git_commit: realiza un commit local explícito solo dentro de las raíces permitidas porSHAWN_CORE_GIT_ROOTS.
El especialista de Changelog está configurado para gpt-5.6-luna, un objetivo de compactación de 64,000 tokens y un techo duro de 100,000 tokens. Estos son un contrato de ejecución para el host que ejecuta el subproceso, no un intento de afirmar que un MCP puede aumentar la ventana de contexto real de un proveedor.
Related MCP server: doc-version-mcp
Ejecutar localmente
python -m unittest discover -s tests -v
$env:SHAWN_CORE_GIT_ROOTS = "<local-repository-root>"
python -m shawn_core_mcp.serverEnvía solicitudes JSON-RPC delimitadas por nuevas líneas a través de la entrada estándar. El servidor es solo local. No abre un puerto, no lee credenciales, no cambia la configuración del modelo ni publica en GitHub.
Límite público
Este repositorio excluye intencionalmente la configuración personal, las rutas de modelos y conjuntos de datos, las credenciales en la nube, el material del cliente, las salidas generadas y las implementaciones privadas de especialistas. La publicación en GitHub la realiza el operador, no el MCP.
Available Tools
8 toolsatlas_continuity_recordC
Write a compact local Atlas Cartographer continuity card beneath SHAWN_CORE_CONTINUITY_HOME.
Inputs: title (required), source (required), summary (required).
changelog_finalizeBRead-onlyIdempotent
Render a receipt-backed end-of-task changelog entry.
Inputs: title (required), changes (required), receipts.
changelog_intakeCRead-onlyIdempotent
Start the Changelog specialist with a Git snapshot, Atlas Cartographer handoff, @github handoff, and Luna execution contract.
Inputs: repo_path (required).
orchestrator_contextARead-onlyIdempotent
Return the public specialist registry and its ownership boundaries.
Inputs: no named parameters.
orchestrator_routeCRead-onlyIdempotent
Route a task or keep it with Orchestrator until a smoke or validation gate identifies a missing capability.
Inputs: task (required).
personal_git_commitA
Plan or explicitly create a local commit inside an allowlisted Git root. This never pushes or publishes.
Inputs: paths (required), message (required), repo_path (required), execute.
personal_git_snapshotARead-onlyIdempotent
Read status and latest commit from an allowlisted local Git repository.
Inputs: repo_path (required).
token_master_auditBRead-onlyIdempotent
Return Token Master's read-only audit contract.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a clearly distinct function: orchestration context vs routing, git snapshot vs commit, changelog intake vs finalize, plus audit and continuity recording. There is no meaningful overlap or ambiguity between the tools.
All names use snake_case with useful domain prefixes, but the second element mixes nouns and verbs: orchestrator_context, changelog_intake, and personal_git_snapshot are noun-style, while orchestrator_route and changelog_finalize are verb-style. The pattern is readable but not consistently verb_noun.
Eight tools is a well-scoped size for the apparent domain of personal orchestration, git snapshots/commits, changelog handling, and continuity tracking. Each tool represents a meaningful capability without excessive fragmentation.
The main workflows are covered: routing and context for orchestration, git snapshot and commit for local changes, changelog intake and finalize for task closure, and a continuity record. Minor gaps exist around updating/reading registry or continuity artifacts, but core workflows have no dead ends.
Related MCP Connectors
Governed local-first memory and continuity for AI agents — signed receipts, optional hosted lane.
Git collaboration for AI agents and people: tasks, hand-offs, reviews, teams, shared memory.
Tenant-scoped control layer for agent-to-agent systems: governed routing, approvals, evidence.
Durable commitment lifecycle, verification, governance and recovery layer for agentic commerce.
Related MCP Servers
- AlicenseCqualityBmaintenanceEnables local-first model routing and persistent tool library management, allowing automated workflow detection and conversion of stable patterns into reusable tools.40Mozilla Public 2.0
- AlicenseAqualityBmaintenanceEnables local-first document versioning with content-addressable storage, word-level AST diffs, and AI-compliance auditing for LLM agents.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to maintain local-first project memory, coordinate task ownership across Git worktrees, and verify completion against project-defined checks with durable evidence stored in the repository.1Apache 2.0
- AlicenseBqualityBmaintenanceEnables Claude Code and Codex hosts to route work to bounded local AI subscription workers through signed-in clients, with saved workflow contracts, evidence checkpoints, reviewed model memory, video and social evidence capture, and bounded failover. Manages long-running tasks via pinned Git worktrees and an external supervisor that can swap a stopped host for another provider's client.5MIT