Skip to main content
Glama
Sign In
event4u-app

@event4u/agent-config

Official
by event4u-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @event4u/agent-config

  • agent-toolbelt

    marras0914
    A
    license
    A
    quality
    C
    maintenance
    Agent Toolbelt is an MCP server exposing 11 focused API tools for LLM agents — schema generation, text extraction, token counting, CSV conversion, Markdown conversion, URL metadata, regex builder, cron expressions, address normalization, color palettes, and brand kits. Each tool is a focused microservice with structured input/output, WCAG-scored color data, USPS address parsing, and multi-model to
    25
    25 npm
    1
    MIT

Related Servers

  • Agent Harness Kit

    WaelBos1796
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides a provider-agnostic MCP server that gives AI coding agents a shared workflow for drafting specs, claiming tracked tasks, logging actions and handoffs, and gating completion on health-check evidence. It also bundles read-only skills for triage, review, consultation, and product guidance across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.
    29 npm
    MIT

  • Cortex Intelligent

    adyoi
    A
    license
    C
    quality
    A
    maintenance
    Enables ordinary LLMs to be augmented fully offline — with no API keys or external services — through model-aware guardrails, exemplar retrieval, structured self-critique, compliance scoring, and an allowlisted verification runner. Also provides hybrid knowledge-base search, decaying long-term memory, and persistent plan/task management across 54 MCP tools usable from any MCP client such as OpenCode, Claude Desktop, Cursor, or VS Code.
    62
    MIT

  • memorix

    AVIDS2
    A
    license
    A
    quality
    A
    maintenance
    Cross-agent memory bridge for AI coding assistants. Persistent knowledge graph shared across 10 IDEs (Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, Gemini CLI) via MCP. 22 tools including team collaboration, auto-cleanup, mini-skills, session management, and workspace sync. 100% local, zero API keys required.
    9
    1,654 npm
    887
    Apache 2.0

  • Fermi

    abel30567
    A
    license
    Not graded
    quality
    C
    maintenance
    A portable AI control plane that lets connected MCP hosts, chat clients, and messaging channels share persistent memory, versioned skills, unified search, permission-gated tools, sandboxed code execution, browser automation, and queued tasks.
    7 npm
    MIT

  • Commander Plus

    yashkhou
    F
    license
    Not graded
    quality
    C
    maintenance
    A local-first MCP control-plane core that gives AI agents persistent project context through workspace registration, reusable skill routing, and health guardians over stdio.
    6,638 npm
    -

  • Coding Tools MCP

    xyTom
    A
    license
    Not graded
    quality
    B
    maintenance
    Empower any MCP-compatible AI Agent(MCP Client) with engineering-grade capabilities to understand, modify, run, and deliver real-world code repositories.
    164 PyPI
    1,216
    Apache 2.0
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.9/5.0

Scored across 26 tools

Disambiguation4/5

Most tools have distinct domains: graph_* (node, dead, impact, path, query, tests_for) are cleanly separated by query shape, and the memory_lookup/memory_get pair is explicitly framed as an index-then-fetch workflow. The only mild overlap is doctor_report vs conformance_check (both install diagnostics), but their descriptions distinguish triage vs a strict contract pass. No two tools appear to do the same thing.

Naming Consistency4/5

Names are uniformly snake_case with a domain prefix, and list_skills/list_commands/list_rules plus chat_history_append/read are strongly parallel. The pattern drifts between verb_noun (list_skills, run_tests, lint_skills) and noun_noun/noun_verb (capabilities_index, roadmap_archive, memory_status), but the domains are legible and no camelCase or mixed conventions appear.

Tool Count3/5

At 26 tools, the set is on the heavy side, though the breadth is real: graph analysis, engineering memory, roadmap tooling, skill/command/rule discovery, diagnostics, telemetry, and chat history. Each tool is defensible on its own, but the count is high enough that an agent must sift across many subsystems to find the relevant operation.

Completeness4/5

Coverage across graph, memory, roadmap, skills, diagnostics, and telemetry is broad and coherent, with read/write pairs for chat history and memory (lookup/get/signal/status). Minor gaps exist — no roadmap creation, no skill/command/rule authoring beyond lint, and read_resource_body is the only body-fetch path — but core workflows are reachable without dead ends.

Resources