Skip to main content
Glama
nami2111

junobuild-mcp-server

by nami2111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to junobuild-mcp-server

No user-submitted related servers found.

    Related Servers

    • docsbook-mcp by Docsbook-io

      docsbook-mcpofficial

      Docsbook-io
      A
      license
      C
      quality
      C
      maintenance
      A proxy MCP server that provides access to ~40 tools for managing a Docsbook workspace, including branding, navigation, SEO/GEO/AEO, AI chat system prompt, translations, analytics, webhooks, and the doc source-of-truth graph via any MCP client.
      62
      MIT
    • meshive-mcp by meshive

      meshive-mcpofficial

      meshive
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      Apache 2.0

    • JoomEngine MCP

      joomengine
      A
      license
      Not graded
      quality
      A
      maintenance
      An embeddable library and self-hosted MCP server for administering Joomla 6.x through bounded, auditable semantic actions via the Joomla Web Services API or a native companion plugin.
      3 npm
      4
      GPL 2.0

    • MCPJungle mcp gateway

      mcpjungle
      A
      license
      Not graded
      quality
      B
      maintenance
      MCPJungle is a self-hosted MCP Registry and Gateway suitable for both local and enterprise deployments. It provides a single URL for your MCP clients to access servers and a central platform for you to track your MCPs and client-server interactions.
      1,272
      Mozilla Public 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

    A3.8/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. The domain prefixes (auth, changes, config, etc.) clearly separate concerns, and within each domain, tools like apply, list, reject are unambiguous.

    Naming Consistency4/5

    Tools follow a consistent juno_<domain>_<action> pattern, with occasional noun-only names (juno_docs, juno_status) and both singular and plural forms. Minor variations exist but the pattern is clear.

    Tool Count5/5

    18 tools cover the main aspects of Juno satellite management (auth, changes, config, functions, hosting, etc.) without being overwhelming. The count feels well-scoped for the domain.

    Completeness4/5

    The tool set covers core workflows: authentication, config management, changes (apply, list, reject), functions lifecycle, hosting operations, and status checks. Missing are direct user/datastore CRUD or config viewing, but these are out of scope for a CLI-focused MCP.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources