Skip to main content
Glama

Related Servers

Alternatives to roiq-os-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables reading and writing Qoder Supabase workspace data—projects, todos, issues, versions, notes, milestones, daily logs, and ideas—from Claude or any MCP-aware client.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Bridges Claude Code to the Rowan Rose CRM, translating MCP tool calls into REST API requests for contacts, cases, documents, and more.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Code to any ObjectStack deployment, enabling discovery, querying, and updating of objects and records, plus running business actions, all under user permissions and row-level security.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents and MCP-speaking clients such as Claude, Cursor, VS Code and Cline read/write access to a workspace through a single token, so they can create pages, query databases, append blocks, apply templates, comment, and upload files in plain language. It runs headless for CI, cron jobs and self-hosted deployments, keeping tool schemas and responses lightweight, with batched mutations, idempotency keys and retry handling built in.
      5,360 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI agents and MCP-speaking clients such as Claude, Cursor, VS Code and ChatGPT to Notion using a single token, enabling them to create and edit pages, query databases, append blocks, apply templates, comment, and upload files in plain language. It runs headless for CI and background agents, keeps context usage low by loading only three tools, and supports batched mutations with idempotency and retries.
      5,360 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 32 tools

    Disambiguation5/5

    Each tool targets a distinct entity and action, with clear boundaries (e.g., roiq_create_db vs roiq_add_column, roiq_montage_edit vs roiq_montage_correct). Even the escape hatch roiq_state_patch is explicitly documented as a last resort, not a source of ambiguity.

    Naming Consistency5/5

    All tools follow a consistent roiq_verb_noun pattern (e.g., add_card, create_db, list_items). Verbs are uniform (add, create, delete, list, get, update, rename) and nouns correspond to domain entities, making the pattern predictable.

    Tool Count4/5

    32 tools is relatively high, but each covers a distinct operation in a comprehensive OS platform (kanban, spaces, pages, video montage, skills). The scope justifies the count, though a few tools (e.g., roiq_state_get, roiq_state_patch) are general-purpose and could have been fewer.

    Completeness4/5

    The tool surface covers CRUD for core entities (cards, columns, properties, pages, spaces, items) and video montage workflow. Minor gaps exist (e.g., no explicit tool for updating page title separately, but roiq_rename_item works; no user management tools), but the escape hatch roiq_state_patch ensures no dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues