Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CONTINUUM_HOMENoOverride the default data directory `~/.continuum/` used by the Continuum MCP server.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_saveC

Save a persistent memory (decision, fact, preference, etc.).

memory_searchB

Search memories with lexical/FTS retrieval.

memory_getC

Get a memory by id.

memory_updateB

Update fields of an existing memory.

memory_deleteA

Delete a memory. Requires confirm=true (high-risk).

memory_recentB

List recent memories for the current or given project.

project_listB

List registered Continuum projects.

project_registerC

Register a local path as a Continuum project.

project_getB

Get a project by id.

project_contextC

Return registered project context, git status, and recent memories.

git_statusB

Git status with protected-branch detection (main/master/production).

git_diffA

Git diff (unstaged by default; set staged=true for index). Large diffs are truncated.

git_logC

Recent commit log.

branch_listB

List local git branches and mark protected ones.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct resource+action: the memory_* family cleanly separates save/search/get/update/delete/recent, project_get vs project_context differ by scope, and git_status/git_diff/git_log/branch_list cover orthogonal git queries. No two tools appear to do the same thing, so an agent can select confidently.

Naming Consistency4/5

Most tools follow a consistent resource_verb snake_case pattern (memory_save, project_register, git_status). The lone deviation is branch_list, which drops the git_ prefix used by its sibling git tools, but overall readability remains high.

Tool Count5/5

14 tools split evenly across three coherent domains (memory, project, git) is well-scoped for a context/memory server. Each tool earns its place without redundancy.

Completeness4/5

Memory CRUD is fully covered (save/get/update/delete/search/recent) plus project lifecycle and git inspection. Minor gaps: no project update/unregister/delete or branch checkout/creation, but core workflows are workable.

Maintenance

ActivityMaintained
ResponsivenessNo issues