RogerRoger MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_peopleB | Retrieve all people/contacts from RogerRoger CRM |
| get_personA | Retrieve a specific person by ID |
| create_personC | Create a new person/contact in RogerRoger |
| update_personC | Update an existing person/contact |
| delete_personC | Delete a person/contact |
| get_tasksC | Retrieve tasks from RogerRoger |
| create_taskC | Create a new task in RogerRoger |
| get_organizationsC | Retrieve all organizations from RogerRoger CRM |
| get_organizationB | Retrieve a specific organization by ID |
| create_organizationC | Create a new organization in RogerRoger |
| update_organizationC | Update an existing organization |
| delete_organizationC | Delete an organization |
| get_listsC | Retrieve all lists/segments from RogerRoger |
| get_listB | Retrieve a specific list/segment by ID |
| create_listC | Create a new list/segment in RogerRoger |
| update_listC | Update an existing list/segment |
| delete_listC | Delete a list/segment |
| get_tagsC | Retrieve all tags from RogerRoger |
| get_tagB | Retrieve a specific tag by ID |
| create_tagC | Create a new tag in RogerRoger |
| update_tagB | Update an existing tag |
| delete_tagC | Delete a tag |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.