ArchLog MCP
Server 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 |
|---|---|
| archlog_check_environmentA | Check the local ArchLog, ENRE-CPP, SemArc, Git, Java, data path, and LLM configuration without starting an analysis. |
| archlog_validate_requestA | Validate and normalize a GitHub C/C++ release range. This performs no checkout and starts no analysis. |
| archlog_start_analysisA | Start an asynchronous architecture-guided release-note analysis and return immediately with a persistent job ID. Poll with archlog_get_status; do not wait in this call. |
| archlog_get_status | Get persisted progress for an ArchLog job. A worker exit alone never means success; only state=succeeded with validated artifacts does. |
| archlog_get_result | Return local release-note and manifest paths only after validating every required Phase 1-3 success artifact. |
| archlog_get_failure_report | Return the truthful failure stage, error, recovery flag, and detailed local log path for a failed job. |
| archlog_resume_analysis | Resume a failed or cancelled job using its existing isolated job directory and checkpoints. |
| archlog_cleanup_intermediate_results | Permanently delete intermediate artifacts for one succeeded job, or all succeeded jobs when job_id is omitted. Retains the traceable release note and minimal MCP metadata. Requires confirm=true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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/hongzhuan/ArchLog-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server