CodeRoot-Authoring-MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SettleTop-Inc/CodeRoot-Authoring-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server