Skip to main content
Glama
Royalti-io

@ikenga/mcp-iyke

by Royalti-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @ikenga/mcp-iyke

No user-submitted related servers found.

    Related Servers

    • mcpfreecad

      tspspi
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that drives a running FreeCAD session, exposing document management, modeling, inspection, snapshot, and optional workbench operations to MCP clients over stdio or authenticated remote HTTP.
      1
      -

    • vred-mcp

      krngrover6
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that enables MCP-compatible AI clients to inspect and control the currently open scene in a running Autodesk VRED Professional 2027 instance via a secure bridge, supporting read-only inspection and gated mutations like selection, visibility, transforms, and screenshots.
      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

    B3.3/5.0

    Scored across 67 tools

    Disambiguation4/5

    Most tools are cleanly separated by domain prefix (todo_, timer_, secret_, kv_, lock_, project_, scratchpad_) and their descriptions pin down exact resources and actions. A few are potentially confusable (iyke_go vs iyke_open, iyke_todo_complete vs iyke_todo_update), but the descriptions draw clear boundaries.

    Naming Consistency3/5

    The strong iyke_ prefix and snake_case domain grouping (todo_create, secret_get, lock_acquire) give a recognizable order, but many UI/interaction tools are bare verbs or nouns (iyke_go, iyke_mode, iyke_dom, iyke_wait, iyke_click, iyke_state). This mix of noun_verb and action-only names is readable but not a single consistent convention.

    Tool Count1/5

    67 tools is far beyond the 50+ extreme threshold, and even though the Ikenga domain is broad, bundling UI automation, projects, sessions, packages, secrets, storage, and locks into one MCP surface creates a heavy selection problem. The count would be more manageable split into smaller domain-specific servers.

    Completeness4/5

    The suite covers full CRUD-style surfaces for KV, scratchpads, secrets, and locks, plus coherent UI automation (state/dom/click/type/wait) and project/session/todo management. Notable gaps exist—no todo delete, no package install, no direct session message/send, and no timer update—but most workflows can proceed or work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources