Skip to main content
Glama
Sign In
munim

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

  • Plugboard

    mikecann
    A
    license
    Not graded
    quality
    B
    maintenance
    A single MCP gateway that lets every agent and login on your machines reach services like Notion, Sentry, Cloudflare, Gmail and Google Calendar after signing in once, with per-agent tokens. Calls that reach other people or can't be undone wait for approval first, and every call is logged.
    92 npm
    18
    MIT

  • 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
    88 npm
    4
    MIT

  • Vibecoders MCP

    RaedBerjaoui
    A
    license
    A
    quality
    D
    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
    4
    MIT
  • monacloud-mcp

    monacloud-mcpofficial

    mona-software
    A
    license
    C
    quality
    B
    maintenance
    A unified MCP server that lets AI agents (Claude Code, Codex, Cursor) deploy web apps and VPS instances, provision Supabase-compatible Postgres/Auth/Storage databases, register DNS domains, and send transactional email using a shared MONA Pass identity and VND wallet. It also embeds MONA Pay tooling for VietQR top-ups, checkout, webhooks and reconciliation, so agents can handle payment requests, budget approvals and resource lifecycles end to end.
    186
    152 npm
    MIT

  • Urumi MCP Gateway

    kazuma761
    A
    license
    Not graded
    quality
    C
    maintenance
    Puts every MCP server a team uses behind a single /mcp endpoint, so clients like Claude Code, Codex, and Cursor reach all aggregated tools with one personal, revocable API key while upstream credentials stay hidden. It routes each call to the right upstream, enforces per-tool permissions, isolates failures, and writes an audit log of who called what, with a bundled WooCommerce server for products and orders.
    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.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

ActivityNo data
ResponsivenessOutdated data

Resources