Skip to main content
Glama
kerbelp

Metatron

by kerbelp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Metatron

Related Servers

  • flaiwheel

    dl4rce
    A
    license
    A
    quality
    A
    maintenance
    Self-hosted memory and governance layer for AI coding agents. 28 MCP tools with hybrid search, structured knowledge capture, behavioral nudges, and git-native storage. Zero cloud dependencies.
    30
    6
    Business Source 1.1

  • Cortex Hub

    lktiep
    A
    license
    Not graded
    quality
    A
    maintenance
    Self-hosted AI Agent Memory + Code Intelligence Platform providing persistent memory, AST-aware code search, and quality enforcement via a single MCP endpoint.
    97
    MIT
  • Trapic Core by trapicAi

    Trapic Coreofficial

    trapicAi
    A
    license
    Not graded
    quality
    D
    maintenance
    Self-hosted MCP server for long-term memory in AI coding assistants, capturing decisions, conventions, and discoveries as structured traces with tag and keyword search.
    2
    MIT

  • Thalamus

    insomnolence
    A
    license
    Not graded
    quality
    B
    maintenance
    Self-hosted MCP server that gives coding agents persistent, code-aware memory with structural graph recall and blast-radius planning. It links experiential decisions to code locations and provides honest measurement instruments.
    Apache 2.0

  • codecortex

    rushikeshmore
    A
    license
    Not graded
    quality
    D
    maintenance
    Persistent codebase knowledge layer for AI agents. Pre-digests codebases into structured knowledge (symbols, dependency graphs, co-change patterns, architectural decisions) and serves via MCP. 28 languages, 14 tools, ~85% token reduction.
    20 npm
    10
    MIT
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct artifact and action: reading decisions vs verification contracts, submitting a new decision candidate vs feedback, and fetching a template. The descriptions clearly delineate read-only retrieval from submission, and there is no functional overlap.

Naming Consistency4/5

All names use snake_case with a verb-first structure (get_, submit_), which is consistent and predictable. Minor deviation: get_decisions_for_context includes a preposition, and some names are multi-word noun phrases, but no mixing of conventions.

Tool Count5/5

Five tools is well within the ideal 3–15 range and each tool serves a distinct, necessary function in the decision/verification workflow. No tool feels redundant or extraneous.

Completeness4/5

The surface covers reading decisions, submitting decision candidates, giving feedback, reading verification contracts, and getting a template. However, there is no way to submit a new verification contract candidate or give feedback on verification contracts, leaving a gap on the verification side of the domain.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources