Skip to main content
Glama
alopez3006

snipara-mcp

by alopez3006
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to snipara-mcp

Related Servers

  • solucortex-mcp by soluai-spa

    solucortex-mcpofficial

    soluai-spa
    A
    license
    A
    quality
    A
    maintenance
    Enables MCP-compatible AI agents to connect to SoluCortex projects, recall relevant technical decisions, conventions, risks, and architecture before working, and record new memories afterward.
    4
    MIT

  • light-agent-memory-mcp-server

    AliYar-Khan
    A
    license
    A
    quality
    B
    maintenance
    Provides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.
    12
    5 npm
    MIT

  • promem-mcp

    DIP-RO
    A
    license
    B
    quality
    A
    maintenance
    Enables AI coding agents to maintain persistent project context, including rules, decisions, environment intelligence, and Git history, using a local-first MCP server with automatic project detection and token-efficient retrieval.
    13
    MIT

  • Tages

    ryantlee25-droid
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI coding agents to maintain persistent, cross-session memory of codebase architecture, naming conventions, and decisions through MCP tools. Eliminates repetitive project re-explanation by automatically injecting stored context into every session with local-first SQLite storage and optional team sharing capabilities.
    4
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 12 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: ask, context query, search, read line range, get chunk, recall memory, remember if novel, end-of-task commit, inbox review queue/plan/apply, and stats. No overlapping functionality.

Naming Consistency5/5

All tools follow a consistent 'snipara_' prefix with snake_case descriptive names (e.g., snipara_context_query, snipara_end_of_task_commit). No mixing of conventions or abbreviations.

Tool Count5/5

12 tools is well-scoped for a documentation and memory management server. It covers viewing, searching, querying, memory operations, inbox review workflow, and statistics without being overwhelming or sparse.

Completeness4/5

The tool surface covers core retrieval, memory storage, and inbox review. Minor gaps include the lack of an explicit update or delete for memories, but the server appears focused on append and recall. Overall coverage is strong.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources