CodeRoot-Authoring-MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_record_schemaA | Return the asset-record.json contract: the fields, their types, and the
rules a valid record must satisfy. A deliberate duplicate of the
|
| record_factsA | Record creation facts you have just decided or just written: language, framework, runtime, direct dependencies, repository identity, creation timestamp. Deep-merges into the existing record, so call it as often as facts arrive. Returns {"record": , "missing": []}, or {"error": "", ...} on rejection. Do NOT use this for created_by, maintained_by or model_access.mode -- those are the author's to confirm via finalize_record. |
| read_recordA | Read the current asset-record.json and report which author-only fields are still missing. Returns {"record": <the record, {} if no file exists yet>, "missing": [...]}, or {"error": "", ...} on rejection. A missing file is a normal state, not an error. |
| finalize_recordA | Mark the asset record complete, before the first push. Requires the
author's own confirmation of created_by, maintained_by and
model_access.mode -- pass them in |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_asset_record | Walk the asset-record workflow: capture facts, review, confirm. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| record_schema_resource | The asset-record.json contract, as JSON Schema. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: schema retrieval, fact recording, record reading, and finalization. There is no functional overlap, and the descriptions explicitly delineate boundaries (e.g., record_facts vs. finalize_record).
All tool names follow a consistent verb_noun pattern (get_, record_, read_, finalize_). The naming is predictable and unambiguous, with no mix of conventions.
Four tools is an appropriate size for a focused authoring workflow. Each tool serves a necessary, non-redundant function, and the count falls well within the ideal 3-15 range.
The tool set covers the complete lifecycle of an asset record: reading the schema, recording facts, reading the current state, and finalizing with author confirmation. No obvious dead ends or missing operations for the stated purpose.