Skip to main content
Glama
vishalsg42

munim

by vishalsg42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to munim

  • Daemoon

    daemoon-dev
    A
    license
    Not graded
    quality
    D
    maintenance
    Gives AI coding agents (Claude Code, Cursor, etc.) unified, secure access to dev infrastructure (Vercel, GitHub, Supabase, Cloudflare, GCP) via a single MCP token.
    MIT

Related Servers

  • devops-mcp

    NotHarshhaa
    A
    license
    B
    quality
    C
    maintenance
    Unified MCP server for DevOps engineers that provides real-time read and write access to Kubernetes, ArgoCD, Prometheus, and PagerDuty from any MCP-compatible AI agent.
    21
    107 npm
    3
    MIT

  • Vibecoders MCP

    RaedBerjaoui
    A
    license
    A
    quality
    C
    maintenance
    One MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.
    23
    3
    MIT

  • Adi MCP

    adityasingh2929
    F
    license
    Not graded
    quality
    B
    maintenance
    A remote MCP server that exposes tools from many services (X, LinkedIn, GitHub, Gmail, Notion, etc.) through a single endpoint on Cloudflare Workers, enabling unified access to third-party APIs via natural language.
    -
  • Lanes Link by lanes-sh

    Lanes Linkofficial

    lanes-sh
    A
    license
    Not graded
    quality
    A
    maintenance
    One secure, self-hosted MCP endpoint connecting AI agents to your real accounts (mail, calendar, files, notes), with per-profile separation, explicit permission enforcement, and an append-only audit log.
    88 npm
    35
    Apache 2.0
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.4/5.0

Scored across 16 tools

Disambiguation5/5

Each tool targets a distinct operation: cross-client queries (ask_across_clients, find_across_clients, audit_all_clients), single-client actions (check, fix, client_status, work_on_client), provider interactions (list_provider_tools, call_provider_tool, call_provider_api), setup workflows (plan_mail_setup, apply_mail_setup), and client management (add_client, connect_provider). Overlapping tools are clearly differentiated by scope (all vs one client, specific check vs full catalogue, open-ended vs predefined).

Naming Consistency4/5

The vast majority of tools follow the verb_noun snake_case pattern (list_clients, find_across_clients, call_provider_tool, apply_mail_setup, etc.). The single exception is 'client_status', which uses a noun phrase instead of a verb-first format, but it is still unambiguous and consistent in style.

Tool Count5/5

16 tools is well-scoped for a client management and email/DNS configuration server. Each tool serves a distinct purpose without redundancy, covering discovery, diagnostics, remediation, provider integration, and workflow orchestration. The count is within the ideal 3-15 range (slightly above but justified by the breadth of functionality).

Completeness4/5

The tool surface covers the full lifecycle: client creation, provider connection, status checks, health audits, targeted fixes, mail setup planning and application, and run monitoring. Minor gaps exist (e.g., no explicit tool to delete a client or disconnect a provider, and no tool to list the check catalogue directly), but these are likely handled through other means and do not cause agent failures in core workflows.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources