threadctx-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THREADCTX_MODE | No | Mode: local (default) or cloud | local |
| THREADCTX_REPO | No | Override repo auto-detection from git remote | |
| THREADCTX_API_KEY | No | API key for cloud mode (required if mode=cloud) | |
| THREADCTX_API_URL | No | Override API URL for self-hosting | https://threadctx.dev/api/v1 |
| THREADCTX_DB_PATH | No | Local mode store path | ~/.threadctx/local.json |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_writeA | Store a learning, decision, fix, or gotcha for this repository so other agents and teammates can find it later. Call this whenever you resolve a non-obvious bug, make an architectural decision, or discover something that would save someone time in the future. |
| memory_queryA | Retrieve relevant past learnings, fixes, decisions, or gotchas from the team's shared memory before starting risky or repeated work — e.g. touching a service that has caused incidents before, or implementing something similar to past work. Call this before, not after. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one for querying past learnings, the other for storing new ones. No overlap or ambiguity.
Both tools follow a consistent memory_verb pattern (memory_query, memory_write), making it predictable and easy to navigate.
Only two tools for a memory/storage server; while minimal, they cover basic read and write operations. The set feels thin but could be sufficient for a focused use case.
The tool surface lacks essential operations like listing all memories, deleting outdated entries, or updating existing ones, leaving significant gaps for typical memory management workflows.