agent-logbook
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB | No | Path to the SQLite database file | .claude/logbook.db |
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 |
|---|---|
| recallA | Retrieve relevant long-term memories for the current task. Call this at
the START of any task before doing work. Returns ranked memories (facts,
decisions, open tasks/questions) within a token budget, plus a count of
open items. |
| rememberA | Persist ONE distilled memory after completing a work block. |
| supersedeA | Replace an outdated memory with an updated one. The old memory is kept in the chain for history (never deleted). Use this when a decision or fact has changed. |
| list_openB | List open tasks and questions (optionally filter by type: 'task' or 'question'). Call when planning what to do next. |
| set_statusB | Mark a task/question as 'done' or 'dropped' (or reopen with 'open'). |
| memory_historyB | Show the full supersession chain for a memory — how a fact/decision evolved over time. Useful for 'why did we think X before?' questions. |
| memory_statsA | Counts of total/live memories and open items. Cheap health check. Also reports token-usage metrics: recall_count, avg_tokens_per_recall, total_tokens_served (lifetime tokens returned by recall), live_corpus_tokens (estimated tokens across all live memories), and savings_ratio (live_corpus_tokens / avg_tokens_per_recall — roughly how many recalls it would take to read the whole corpus instead of a budgeted slice; null if no recalls have happened yet). |
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
- 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/Rajwantmishra/agent-logbook'
If you have feedback or need assistance with the MCP directory API, please join our Discord server