worklog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKLOG_URL | No | If set, POST events here instead of writing to a file. Endpoint is <WORKLOG_URL>/api/agent/events. | |
| WORKLOG_FILE | No | Where to append events when no receiver is set (i.e., no WORKLOG_URL). Defaults to .worklog/events.jsonl. | .worklog/events.jsonl |
| WORKLOG_API_KEY | No | Bearer token. Required when WORKLOG_URL is set. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_workA | Log a unit of work when you finish something meaningful. Capture the WHY and any open loops — git already has the diff. |
| record_decisionA | Record an architecturally consequential decision (ADR-style). Only call when a real choice was made. |
| report_test_runB | Report the outcome of a test/verify run (counts, not full logs). |
| link_prC | Link a pull request to this project's work log. |
| update_progressB | Upsert the current status of a work item (feature/task). Overwrites the item's status; also records the change. |
| sync_docA | Sync a long-form project document (plan/spec/progress/runbook/research) as rendered markdown. Upserts by (kind, key); the version bumps each sync. Use for docs an agent maintains in-repo, so the log carries their current state. |
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/aadityakushwaha/worklog-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server