roiq-os-mcp
Related Servers
Alternatives to roiq-os-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceBridges Claude Code to the Rowan Rose CRM, translating MCP tool calls into REST API requests for contacts, cases, documents, and more.-
- AlicenseNot gradedqualityCmaintenanceConnects 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
- AlicenseAqualityDmaintenanceEnables Claude Code and other MCP clients to manage bookmarks, collections, and tags in Raindrop.io accounts via natural language.152MIT
- FlicenseBqualityNot gradedmaintenanceBridges Claude Code to a Cloud Orchestrator API, providing access to multi-AI consensus, web search, code execution sandboxes, long-term memory, knowledge graphs, deployment management, and 20+ integrated AI and developer tools.28-
- AlicenseNot gradedqualityDmaintenanceConnects Claude Code with GoHighLevel CRM to manage contacts, pipelines, calendars, conversations, workflows, funnels, and forms via natural language.MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Google Sheets, Docs, Slides, and Drive through a remote MCP server hosted on Cloudflare Workers, with OAuth authentication and Claude-native connect.-
TDQS
Scored across 32 tools
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.
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.
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.
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.