Skip to main content
Glama
aumsuthar

aum-mcp-server

by aumsuthar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aum-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP Coordinator

      CyberClash
      A
      license
      Not graded
      quality
      D
      maintenance
      Acts as a proxy for multiple MCP servers, reducing context window usage from 15,000+ tokens to ~500 tokens by dynamically loading servers on-demand and exposing only 3 tools instead of all tool definitions.
      5
      GPL 3.0

    • dispatch-agent

      abhinav-mangla
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that delegates filesystem operations to a specialized React agent, reducing context usage and improving accuracy for AI applications like Claude Code.
      5 npm
      3
      MIT

    • codex-dobby-mcp

      Averyy
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that lets Claude delegate scoped work to Codex with structured results and guardrails, supporting planning, code review, build, reverse engineering, and long-running background tasks.
      11
      MIT

    • mcp-local-llm

      semenenkod333
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that allows Claude Code to offload mechanical tasks such as summarization, classification, and drafting to a local LLM, reducing API costs while keeping Claude in control of complex reasoning and quality review.
      5 npm
      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

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Tools are cleanly divided into two distinct domains: notes (set/get/list/delete) and Office documents (Word read/create, PowerPoint read/create). Within each domain, actions are clearly differentiated, with no overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent pattern: resource prefix (note_, word_, ppt_) followed by a verb in snake_case. This makes the tool set predictable and easy to navigate for both humans and agents.

    Tool Count5/5

    With 8 tools spanning two focused areas, the count is well-scoped. Each tool serves a clear, necessary function without redundancy, and the server avoids being overly large or sparse.

    Completeness4/5

    Notes have full CRUD coverage. For Word and PowerPoint, read and create are covered, but there are no tools for updating existing documents or deleting them. This is a minor gap, but the core workflows (viewing and creating documents) are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources