SkullRender-Agents MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKFLOW_ROOT | No | Optional. Root directory for configuration (manifests and schemas). Defaults to the repository directory. Can also be set via the --root CLI option. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| skflow_agents_listA | List declarative agent manifests (spine / Saep / Sae / legacy expertos). |
| skflow_agent_getA | Get full YAML text of one agent manifest by id. Use skflow_agents_list for available ids. |
| skflow_packs_listA | List Legion personality packs (PackLich, PackGentleman, PackCerbero). Injected on-demand into offices. |
| skflow_pack_getA | Get full YAML of one personality pack by id (e.g. PackLich). |
| 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. |
| skflow_brief_validateA | Validate a Presentador→Orquestador brief (JSON object or YAML/JSON string). Deterministic check mirroring schemas/brief.schema.json (no LLM). |
| skflow_brief_schemaA | Return the JSON Schema used to validate Presentador⇄Orquestador briefs (for prompting engineers). |
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 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.