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.
    58
    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.
    13 npm
    8
    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.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: fetching decisions, submitting candidates, and providing feedback. There is no overlap in functionality.

Naming Consistency5/5

All tool names follow a verb_noun pattern (get_decisions_for_context, submit_candidate_decision, submit_feedback), with consistent use of 'get' and 'submit'.

Tool Count5/5

Three tools are well-scoped for managing engineering decisions: retrieval, submission, and feedback. The count feels neither too few nor too many.

Completeness5/5

The tool surface covers the full lifecycle for an agent: get decisions for context, submit new candidates, and give feedback. No obvious gaps for the intended use case.

Maintenance

ActivitySlowing
ResponsivenessResponsive

Resources