@octri/cli
OfficialRelated Servers
Alternatives to @octri/cli
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceComprehensive API development and testing MCP server for Claude Code. Integrates OpenAPI parsing, testing, SDK generation, and documentation generation into Claude workflows.81MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language, using a hosted OAuth-authenticated endpoint or a local stdio package. It also ships an OpenAPI codegen tool for generating MCP tools from any OpenAPI spec.1,958 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP 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.34 npm3MIT
- AlicenseBqualityDmaintenanceMCP 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.73 npm19MIT
- AlicenseNot gradedqualityCmaintenanceConverts 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.9 npmMIT
- AlicenseAqualityDmaintenanceA 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.6MIT
TDQS
Scored across 31 tools
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.
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.
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.
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.