Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to delimit

  • agenthelm

    jayasukuv11-beep
    A
    license
    A
    quality
    C
    maintenance
    Shared, versioned memory and governance control plane for AI coding agents. Compiler pipeline resolves architectural decision conflicts across Claude Code, Cursor, and custom agent fleets.
    3
    6
    MIT

  • PeerBridge MCP

    Hoylon
    A
    license
    Not graded
    quality
    A
    maintenance
    Connects multiple AI agents (Codex, Claude Code, Grok, etc.) into a coordinated, auditable team with shared memory, task ownership, and human oversight, enabling parallel collaboration without conflicts.
    238
    Apache 2.0

Related Servers

  • Agent Squad Bridge

    kagtgi
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables multiple AI coding CLIs (Claude Code, Gemini/Antigravity, Codex, and OpenCode) to collaborate as a coordinated team by routing cross-agent prompts, sharing messages and review tickets, tracking tasks on a shared store, and isolating each agent in its own Git worktree with turn-budget safeguards—all inspectable and steerable from a local web dashboard.
    MIT

  • EX MCP Server

    Zazzles2908
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    Provides unified development tools including code analysis, debugging, refactoring, documentation, testing, and project automation through multiple LLM providers (KIMI, GLM, OpenRouter). Features agentic audit capabilities with multi-model consensus for finding issues and generating direct fixes.
    Apache 2.0

  • coding-agents-mcp

    funkyfunc
    A
    license
    C
    quality
    B
    maintenance
    Enables delegating coding tasks to multiple AI CLI agents (Claude Code, Antigravity, Codex, Cursor) with session memory and diff inspection.
    16
    41 npm
    MIT

  • MCP Memory Server

    keleshteri
    A
    license
    B
    quality
    D
    maintenance
    Gives AI coding assistants persistent memory, safety controls, and project awareness by tracking coding sessions, protecting critical files from modifications, and managing approval workflows with automatic changelog generation.
    19
    13 npm
    MIT

  • Zen MCP Server

    salvadorthebrown
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    Orchestrates multiple AI models (Gemini, OpenAI, Claude, local models) within a single conversation context, enabling collaborative workflows like multi-model code reviews, consensus building, and CLI-to-CLI bridging for specialized tasks.
    -
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

A3.8/5.0

Scored across 213 tools

Disambiguation2/5

Multiple tool families have genuinely fuzzy boundaries (session_handoff vs soul_capture vs handoff_create; memory_store vs context_write vs vault_snapshot; review vs audit vs deliberate) and there are many near-identical status/health tools plus seven _impl dispatchers that duplicate their aliases. The verbose when-not-to-use text helps, but with 213 tools an agent will still frequently misselect.

Naming Consistency4/5

Nearly every tool follows a predictable delimit_<domain>_<action> pattern in lowercase snake_case, with clear domain groups like ledger_*, agent_*, gov_*, deploy_*, and obs_*. The main deviations are the underscore-prefixed _delimit_*_impl dispatchers and a few standalone verb-only tools, but there is no chaotic mixing of styles.

Tool Count1/5

213 tools is far beyond any reasonable MCP server surface and exceeds the 50+ extreme threshold by a wide margin. Many tools are thin aliases, duplicate dispatchers, or narrowly-scoped internal helpers that could be collapsed into a small number of parameterized domain tools.

Completeness4/5

For its broad all-in-one platform purpose, the surface is remarkably complete: deploy, governance, ledger, secrets, agent lifecycle, observability, security, social, content, and repo workflows all have their main CRUD/lifecycle operations, and cross-tool chains reference existing tools. Minor gaps are mostly intentional (append-only stores, no hard deletes, some experimental tools) rather than dead ends.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources