jamgate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JAMGATE_HOST | No | Interface to bind in remote mode. Keep it on localhost behind a reverse proxy. | 127.0.0.1 |
| JAMGATE_HTTP | No | 1/true enables remote mode. | off |
| JAMGATE_PORT | No | Port for remote mode. | 8420 |
| JAMGATE_OAUTH | No | In remote mode, serve the MCP OAuth flow so claude.ai / the Claude app can connect. | on |
| JAMGATE_STORE | No | Path to the memory store file. | ~/.jamgate/memory.json |
| JAMGATE_TOKEN | No | Bearer token required in remote mode. The server refuses to start without it. | |
| JAMGATE_GATE_LOG | No | off disables the local decision log. | on |
| JAMGATE_EMBEDDINGS | No | off disables the semantic layer even if the model is installed. | auto |
| JAMGATE_OAUTH_STORE | No | Path to the OAuth state file. | ~/.jamgate/oauth.json |
| JAMGATE_DUP_THRESHOLD | No | Semantic near-duplicate sensitivity (0–1); higher = stricter. | 0.88 |
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 |
|---|---|
| save_memoryA | Save a durable memory about the user through the Jamgate quality gate. Only call this for things worth remembering across sessions — identity, projects, preferences, lasting state — not chatter. Trivial or duplicate input is rejected by the gate. |
| recall_memoryC | Recall stored memories about the user relevant to a query. |
| forget_memoryA | Delete a stored memory by the id shown in recall_memory output. The full id is safest; an unambiguous prefix of 8+ characters also resolves. |
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 3 tools
Each tool targets a distinct memory operation—save, recall, forget—with no functional overlap.
All tools follow a consistent verb_noun pattern (save_memory, recall_memory, forget_memory).
Three tools are perfectly scoped for a core memory management server—neither sparse nor excessive.
Covers create, read, and delete operations but lacks an explicit update tool, though save may implicitly overwrite.