Skip to main content
Glama
OctriDev

@octri/cli

Official
by OctriDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @octri/cli

No user-submitted related servers found.

    Related Servers

    • openapi-mcp

      ceski23
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.
      7 npm
      3
      MIT

    • sufetch

      productdevbook
      A
      license
      B
      quality
      C
      maintenance
      MCP server that enables AI assistants to explore and generate code for type-safe OpenAPI clients from various cloud APIs like DigitalOcean, Hetzner Cloud, and Ory.
      7
      1 npm
      18
      MIT

    • openapi-to-mcp

      Karlangas12
      A
      license
      Not graded
      quality
      B
      maintenance
      Converts any OpenAPI 3.x spec into a live MCP server, making every endpoint a validated tool that AI agents can call without writing glue code.
      5 npm
      MIT

    • SpecBridge MCP

      heecheon92
      F
      license
      A
      quality
      D
      maintenance
      A clone-and-own MCP server that exposes OpenAPI/Huma contract intelligence to AI agents by turning API specifications into deterministic endpoint metadata, schemas, validation facts, and TypeScript declarations.
      6
      -
    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

    B3.2/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have crisp, distinct purposes (e.g. preview_sdk vs trigger_build, push_spec vs import_spec_url vs validate_spec). The only mild overlap clusters are the monitoring_* trio and the build lifecycle tools, but their descriptions clearly delineate when to reach for each.

    Naming Consistency4/5

    Nearly all tools follow an octri_ + verb_noun snake_case pattern (list_projects, get_build, push_spec, trigger_build). A few deviate by prefixing a namespace noun instead of a verb (octri_monitoring_summary, octri_monitoring_releases, octri_whoami, octri_diff_builds), but the convention stays readable and predictable.

    Tool Count3/5

    31 tools is on the heavy side and exceeds the comfortable range. The scope is genuinely broad (specs, SDK settings, builds, artifacts, monitoring, docs), so most tools arguably earn their place, but the surface is large enough that selection burden is real.

    Completeness4/5

    The surface covers the full lifecycle well: spec ingestion/validation, settings read/write, build trigger/poll/retry/fetch, artifact inspection, monitoring, issues, logs, docs, and MCP discovery. Minor gaps exist (no delete/cleanup for specs or builds, no project creation), but core workflows are complete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources