Shawn Core MCP
Route tasks, audit token config, manage changelogs, record continuity, and snapshot/commit local Git repos.
orchestrator_route – Route a task to the first specialist or keep with Orchestrator until a validation gate identifies a missing capability.
orchestrator_context – Return the public specialist registry and ownership boundaries.
token_master_audit – Inventory token-relevant local configuration facts.
changelog_intake – Start a changelog subprocess with Git snapshot, Atlas Cartographer handoff, and @github handoff.
changelog_finalize – Render a receipt-backed changelog entry at task end.
atlas_continuity_record – Write a compact local continuity card beneath SHAWN_CORE_CONTINUITY_HOME.
personal_git_snapshot – Read status and latest commit from an allowlisted local Git repository.
personal_git_commit – Plan or explicitly create a local commit inside an allowlisted Git root (never pushes/publishes).
Provides tools for working with local Git repositories, including reading repository status and latest commit, and making explicit commits within allowlisted repository roots.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Shawn Core MCP start a changelog intake for this task"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Shawn Core MCP
Shawn Core MCP is a local-first JSON-RPC MCP server for practical specialist routing, continuity, and evidence-based handoffs.
The public orchestrator is named Orchestrator. It retains a concise map of every specialist for ordinary tasks and escalates only when deeper proof is needed. That keeps routing helpful without turning every small request into a multi-agent ceremony.
Every public specialist has the same 8/10 contract baseline: intake, evidence, handoff, and public boundary. This measures public operational completeness, not a claim that every domain has identical technical depth.
Included core tools
orchestrator_route: return the first specialist and validation plan, including themok-routerlane for resource-aware model/backend dispatch.token_master_audit: inventory token-relevant local configuration facts.changelog_intake: start a lightweight changelog subprocess plan with an Atlas Cartographer handoff, a local Git snapshot, and an@githubhandoff.changelog_finalize: render a receipt-backed changelog entry at task end.atlas_continuity_record: write a compact, payload-free Cartographer card beneath an operator-selected local continuity root.personal_git_snapshot: read status and latest commit from an allowlisted local Git repository.personal_git_commit: make an explicit local commit only within roots allowlisted bySHAWN_CORE_GIT_ROOTS.
The Changelog specialist is configured for gpt-5.6-luna, a 64,000-token
compaction target, and a 100,000-token hard ceiling. Those are an execution
contract for the host that runs the subprocess, not an attempt to claim that
an MCP can raise a provider's actual context window.
Related MCP server: doc-version-mcp
Run locally
python -m unittest discover -s tests -v
$env:SHAWN_CORE_GIT_ROOTS = "<local-repository-root>"
python -m shawn_core_mcp.serverSend newline-delimited JSON-RPC requests over standard input. The server is local only. It does not open a port, read credentials, change model settings, or publish to GitHub.
Public boundary
This repository intentionally excludes personal configuration, model and dataset paths, cloud credentials, client material, generated outputs, and private specialist implementations. GitHub publication is performed by the operator, not by the MCP.
MoK router boundary
Model Operating Kernel is the dedicated router/runtime specialist beneath Orchestrator. Orchestrator owns the whole user problem; MoK owns model/backend selection, resource checks, dispatch, bounded fallback, and execution receipts. Kairo remains a separate reasoning/research line and may be routed to as an expert rather than becoming the routing layer itself.
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.
Maintenance
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