RogerRoger MCP Server
OfficialRelated Servers
Alternatives to RogerRoger MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage GoHighLevel CRM data including contacts, conversations, opportunities, calendars, and forms through MCP tools and resources.51AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and write CRM data—companies, contacts, opportunities, tasks, and interactions—through MCP, with OAuth and provenance tracking for every value.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage a fully customizable CRM, including contacts, companies, sales pipelines, custom objects and fields, file uploads, and data relationships via MCP over HTTP.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to perform go-to-market workflows such as company and contact enrichment, CRM querying, and controlled, audited writes to a CRM through MCP tools callable from any MCP client.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with multiple CRM systems through a unified set of MCP tools, such as finding contacts, accounts, and deals, while supporting mock, REST, and vendor-specific backends.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage CRM prospects, activities, reminders, and mailbox via natural language commands through the Model Context Protocol.3MIT
TDQS
Scored across 22 tools
Each tool targets a distinct resource (people, tasks, organizations, lists, tags) with a clear action (get_/create_/update_/delete_). No two tools appear to do the same thing. The distinction between get_people (all) and get_person (specific by ID) is clear.
All tool names follow a strict verb_noun snake_case convention throughout: get_/create_/update_/delete_ as the verb prefix, followed by the resource name. The naming is perfectly predictable and consistent across all 22 tools.
22 tools is at the high end but still reasonable for a CRM server covering 5 distinct resource types (persons, tasks, organizations, lists, tags) each with CRUD operations. The number is slightly heavy but each tool earns its place.
The people, organizations, lists, and tags resources have full CRUD coverage. However, tasks have only get_tasks and create_task - missing get_task by ID, update_task, and delete_task. This is a notable inconsistency in lifecycle coverage across resource types.