Shawn Core MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHAWN_CORE_GIT_ROOTS | No | Allowlisted local Git repository root(s) used by personal_git_snapshot and personal_git_commit. Example: <local-repository-root>. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orchestrator_contextA | Return the public specialist registry and its ownership boundaries. |
| orchestrator_routeC | Route a task or keep it with Orchestrator until a smoke or validation gate identifies a missing capability. |
| token_master_auditB | Return Token Master's read-only audit contract. |
| personal_git_snapshotA | Read status and latest commit from an allowlisted local Git repository. |
| changelog_intakeC | Start the Changelog specialist with a Git snapshot, Atlas Cartographer handoff, @github handoff, and Luna execution contract. |
| changelog_finalizeB | Render a receipt-backed end-of-task changelog entry. |
| atlas_continuity_recordC | Write a compact local Atlas Cartographer continuity card beneath SHAWN_CORE_CONTINUITY_HOME. |
| personal_git_commitA | Plan or explicitly create a local commit inside an allowlisted Git root. This never pushes or publishes. |
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 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.