Skip to main content
Glama
Sign In
ycli

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ycli

No user-submitted related servers found.

    Related Servers

    • iPaaS MCP Server

      providcc
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes 20 read/write tools that let IDE and agent users search the interface catalog, build and validate flow-model JSON, import OpenAPI specs, run ETL tasks, and plan or revoke service permissions on RestCloud-compatible integration platforms. Writes default to dry-run and every call is written to a desensitized jsonl audit trail.
      MIT

    • yandex-tracker-mcp-lite

      tonysafonov
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to work with Yandex Tracker issues — searching, reading with comments and attachments, creating, updating, commenting, transitioning and linking — using compact responses and an escape-hatch request tool that reaches the rest of the Tracker API v3. Setup is a single command with OAuth token and organisation id configuration.
      MIT

    • Enlace

      Caelos-Palacio
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes four stdio tools that let an agent research an application's documented interface, produce a validated single-use plan, and execute read-only operations against public HTTP JSON APIs, static HTML/JSON/text sources, and host-configured CLIs. Runs in-process with no listening port, accounts, or model dependency, returning bounded results while keeping inputs and outputs inside a host-enforced research-plan-execute lifecycle.
      MIT
    • Evo CRM MCP

      Evo CRM MCPofficial

      sistemabritto
      A
      license
      B
      quality
      B
      maintenance
      Enables assistants to read and modify contacts, conversations, messages, pipelines, tasks, inboxes, and AI agents through the CRM REST API, using separate read-only or read-write tool sets. Runs over local stdio or stateless Streamable HTTP with token-based scope separation.
      17
      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

    C2.9/5.0

    Scored across 457 tools

    Disambiguation2/5

    Many tools overlap heavily: issue list/search/count/suggest, worklog list/search/global, wiki comment list/thread variants, multiple DataLens chart get/update/delete tools split by chart type, and direct vs inherited permission tools. Detailed descriptions often label siblings, but with 457 tools the boundaries blur and misselection is likely.

    Naming Consistency3/5

    Most names follow a snake_case service_resource_action pattern, but there are notable deviations such as tracker_me_get, status_get, schema_get, tracker_bulk_issues_list versus tracker_issues_update_bulk, and inconsistent noun/verb ordering. The pattern is still mostly readable, but not uniformly applied.

    Tool Count1/5

    457 tools is an extreme mismatch for any server, far beyond the 3-15 well-scoped range and well past the 25+ threshold. The surface spans Tracker, Wiki, Forms, and DataLens with many experimental and rarely used operations, making the set unwieldy.

    Completeness3/5

    Core CRUD coverage exists for many resources, but there are conspicuous gaps: dashboards have create and one widget tool but no list/get/delete, several org-global objects have no delete endpoint, and some binary download operations are CLI-only. Agents can work around some gaps, but notable dead ends remain.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources