SkullRender-Agents MCP Server
This server manages declarative agent/office manifests and validates structured briefs for MCP-enabled IDEs (VS Code, Cursor, Copilot). You can:
List all agent manifest IDs (
skflow_agents_list) available in the configuredSKFLOW_ROOT.Retrieve a specific agent manifest (
skflow_agent_get) as raw YAML.List and retrieve personality packs (
skflow_packs_list,skflow_pack_get) – optional legacy packs for flavor injection.Resolve an office’s identity (
skflow_identity_resolve) into a prompt block for subagents; optionally inject a personality pack (disable for Scope B neutral environments).Validate a brief (
skflow_brief_validate) deterministically against the built-in schema – supports JSON/YAML string or object.Get the brief JSON Schema (
skflow_brief_schema) used for validation and brief engineering.
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., "@SkullRender-Agents MCP Server validate this brief against the schema"
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.
SkullRender-Agents (@skullrender/mcp-agents)
What this is (plain language):
An MCP (Model Context Protocol) server that loads office manifests from a folder (SKFLOW_ROOT) and exposes tools (skflow_*) so Copilot / Cursor can list offices, resolve identity, and validate briefs.
Two modes:
Mode |
| What you get |
Scope B neutral (recommended for VS Code) | Sibling |
|
Legacy Legion (this repo default) | This repo’s own |
|
Governance rules (Architect / Implementer / Security Guardian) live in Capa A:
https://github.com/crozzbite/WorkDesktop/tree/governance/vscode-copilot-ready
Install
Prerequisites
Node.js 18+ (run
bundle/cli.js)Bun preferred for install / test / bundle. If
bun installfails,npm install— never commitpackage-lock.jsonnext tobun.lockFor Scope B: clone office-accelerator as a sibling folder (same parent directory)
cd $env:USERPROFILE\Documents # any parent you choose — do not hardcode into git
git clone https://github.com/crozzbite/SkullRender-Agents.git
git clone https://github.com/crozzbite/office-accelerator.git
cd SkullRender-Agents
bun install
# if Bun fails: npm install (do not git-add package-lock.json)
bun test src/
bun run bundleOptional env (only if folders are not siblings):
[Environment]::SetEnvironmentVariable("SKFLOW_AGENTS_CLI", "<parent>\SkullRender-Agents\bundle\cli.js", "User")
[Environment]::SetEnvironmentVariable("SKFLOW_ROOT", "<parent>\office-accelerator\dist\legion-neutral", "User")Never commit C:\Users\… paths in MCP JSON.
Related MCP server: MCP Harbor
Use
A) Scope B neutral (VS Code) — preferred portable path
Do not point MCP at this repo’s default manifests. Use the accelerator wrapper (resolves paths without hardcoding):
Follow office-accelerator README → copy
templates/mcp.vscode.json.example→.vscode/mcp.jsonThat script sets
SKFLOW_ROOTtodist/legion-neutral(or env override) and runs:
node <sibling>/SkullRender-Agents/bundle/cli.js mcp --root <SKFLOW_ROOT>Policy:
inject_pack: falsealways. Ignoreskflow_packs_*as source of truth.
B) Legacy Legion (this repo as root)
cd SkullRender-Agents
node bundle/cli.js mcp
# or: node bundle/cli.js mcp --root .Tools (skflow_*)
Tool | Purpose |
| List office ids in current |
| Raw YAML by id |
| Office (± pack) → prompt block |
| Deterministic brief check |
| Brief JSON Schema |
| Packs when |
Verify
bun test src/
bun run bundle
Test-Path .\bundle\cli.jsWith Scope B sibling promoted:
cd ..\office-accelerator
bun run smoke:neutralExpect PASS: AgentsManager loadAll=10 against dist/legion-neutral.
Deploy / publish
Not a cloud service. Publish = push master with a working bundle/ story (consumers run bun run bundle locally).
bun test src/
bun run bundle
# Human gate: commit + pushDo not commit machine-specific MCP absolute paths. Prefer accelerator’s ${workspaceFolder} wrapper.
Claude Code helper (writes local Claude MCP — review paths before sharing machines):
node bundle/cli.js setup claude-codeTroubleshooting (Windows / OneDrive)
If @modelcontextprotocol/sdk lands without dist/:
Delete
node_modulesandbun installagain here.Or copy the SDK subtree from
skullrender-mcp-skills/node_modules/@modelcontextprotocol/sdk.
Layout
Path | Role |
| Default/legacy Legion offices |
| Optional personality packs |
| brief / identity / pack schemas |
| MCP entry (after |
Prompt for Copilot / other LLMs (paste after clone)
--- BEGIN SETUP PROMPT (SkullRender-Agents runtime) ---
You are wiring the MCP runtime for Scope B neutral offices.
This repo: https://github.com/crozzbite/SkullRender-Agents
Sibling product: https://github.com/crozzbite/office-accelerator (dist/legion-neutral)
Optional governance: https://github.com/crozzbite/WorkDesktop/tree/governance/vscode-copilot-ready
Hard rules:
- No C:\Users\… paths committed to git.
- For VS Code portable use, SKFLOW_ROOT must be office-accelerator/dist/legion-neutral (or env), NOT this repo’s legacy manifests/packs as SoT.
- inject_pack = false always for Scope B. Packs are not the source of truth.
- Prefer office-accelerator/scripts/mcp-offices.ps1 + templates/mcp.vscode.json.example over hand-written absolute MCP JSON.
Steps:
1) bun install && bun test src/ && bun run bundle in this repo
2) Confirm sibling office-accelerator exists; if not, give clone URL and sibling layout
3) In office-accelerator: bun install && bun run promote:neutral && bun run smoke:neutral
4) Configure VS Code MCP via accelerator template (workspaceFolder script)
5) Smoke: skflow_agents_list → exactly 10 Office* ids; resolve OfficeArchitecture with inject_pack false; brief_validate a minimal brief
6) If list shows Saep*/experto_*, SKFLOW_ROOT is wrong (legacy root) — fix root, do not “neutralize” by renaming in chat
Report PASS/FAIL per step with evidence. No product code changes unless I ask.
--- END SETUP PROMPT ---Related
Pack-free generator: https://github.com/crozzbite/office-accelerator
Skills MCP sibling: https://github.com/crozzbite/skullrender-mcp-skills (
skills_*)Portable Copilot governance: https://github.com/crozzbite/WorkDesktop/tree/governance/vscode-copilot-ready
Available Tools
7 toolsskflow_agent_getA
Get full YAML text of one agent manifest by id. Use skflow_agents_list for available ids.
Inputs: id (required).
skflow_agents_listA
List declarative agent manifests (spine / Saep / Sae / legacy expertos).
Inputs: no named parameters.
skflow_brief_schemaA
Return the JSON Schema used to validate Presentador⇄Orquestador briefs (for prompting engineers).
Inputs: no named parameters.
skflow_brief_validateA
Validate a Presentador→Orquestador brief (JSON object or YAML/JSON string). Deterministic check mirroring schemas/brief.schema.json (no LLM).
Inputs: brief (required).
skflow_identity_resolveA
Resolve office identity (+ optional personality pack) into a prompt block for Cursor subagents. Pack defaults from manifest.personality_pack or pack.inject_default_into.
Inputs: id (required), inject_pack.
skflow_pack_getA
Get full YAML of one personality pack by id (e.g. PackLich).
Inputs: id (required).
skflow_packs_listA
List Legion personality packs (PackLich, PackGentleman, PackCerbero). Injected on-demand into offices.
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 7 tools
Each tool targets a distinct resource and operation: listing/getting agents, listing/getting packs, resolving identities, and validating/retrieving schemas for briefs. There is no overlap or ambiguity between them.
All tools share the 'skflow_' prefix and mostly follow a resource_action pattern. The only deviations are 'skflow_brief_schema' lacking an explicit verb and the singular/plural inconsistency between list and get (e.g., 'agents_list' vs 'agent_get').
With 7 tools, the server is well-scoped for its purpose—covering agent manifests, personality packs, identity resolution, and brief validation—without being bloated or too sparse.
The tool set provides a complete read-oriented workflow for the domain: list and get for both agents and packs, a resolution function, and validation with its accompanying schema. No obvious gaps or dead ends are apparent.
Maintenance
Related MCP Connectors
Immutable agent diagrams: create, edit, validate and render versioned diagrams over MCP.
Agent-native registry to discover APIs, MCP servers and CLIs, with live health checks.
Live behavioral security verifier, schema auditor, and trust oracle for A2A, MCP & x402 agents.
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables centrally authoring and validating reusable agent guidance and delivering it across MCP-compatible hosts via registry resources, prompt templates, skill execution, and shared state.7MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents and projects to register identities, publish and discover contract manifests (berths), resolve dependencies and check compatibility, and subscribe to or broadcast contract-change notifications over MCP tools and resources. It also supports isolated agent-to-agent messaging and an admin overview of participants, berths, subscriptions, and audit history.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP hosts to run a user-configurable agent with multi-engine orchestration, declarative connectors to third-party APIs, task-graph execution, audit ledger, and memory, without needing to clone or configure multiple repositories.27 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to discover offers, retrieve schemas, validate JSON blueprints, preview plugins, and compile deterministic plugin packages as portable artifacts without publishing or mutating third-party systems.-