Skip to main content
Glama

Server Details

Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
opcastil11/rogerthat
GitHub Stars
1
Server Listing
RogerThat

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • Changedsend5 fields changed
      • addedInput schema / properties / attachments
        Added value: +{
        +  "description": "Optional inline attachments — up to 4 per message, ≤512KB base64 TOTAL across all of them (~380KB raw). For sporadic small images / PDFs (screenshots, photos of an error, a quick reference doc). The /remote phone UI renders images inline and PDFs as a download link. For anything bigger, host externally and paste the URL in the message body — RogerRat does NOT host files separately.",
        +  "items": {
        +    "properties": {
        +      "data_base64": {
        +        "description": "Base64-encoded file bytes. Standard alphabet, whitespace ignored.",
        +        "type": "string"
        +      },
        +      "filename": {
        +        "description": "Optional display name.",
        +        "maxLength": 128,
        +        "type": "string"
        +      },
        +      "mime": {
        +        "description": "MIME type. Only the listed types are accepted; others get 400.",
        +        "enum": [
        +          "image/jpeg",
        +          "image/png",
        +          "image/webp",
        +          "image/gif",
        +          "application/pdf"
        +        ],
        +        "type": "string"
        +      }
        +    },
        +    "required": [
        +      "mime",
        +      "data_base64"
        +    ],
        +    "type": "object"
        +  },
        +  "maxItems": 4,
        +  "type": "array"
        +}
      • changedInput schema / properties / message / description
        Previous value: -"Message text. Max 8192 chars."New value: +"Message text. Max 8192 chars. May be empty if at least one attachment is provided."
      • changedInput schema / properties / suggested_replies / description
        Previous value: -"Optional array of up to 4 short canned replies (max 64 chars each). Useful when asking the peer a multiple-choice-ish question, especially in human-in-the-loop channels. E.g. send 'shall I deploy?' with suggested_replies=['yes', 'no', 'show me the diff']. The 'click' from a receiver is just a normal /send with that text."New value: +"Optional array of up to 4 short canned replies (max 64 chars each). Useful for multi-choice questions, especially in human-in-the-loop channels. The 'click' from a receiver is just a normal /send with that text."
      • changedInput schema / properties / to / description
        Previous value: -"Recipient: callsign, '#N' index, or 'all' for broadcast."New value: +"Recipient: callsign, '#N' index, or 'all' for broadcast. Default: 'all'."
      • changedInput schema / required
        Previous value: -[
        -  "to",
        -  "message"
        -]New value: +[
        +  "message"
        +]
  2. 1 tool update
    • Changedsend1 field changed
      • addedInput schema / properties / suggested_replies
        Added value: +{
        +  "description": "Optional array of up to 4 short canned replies (max 64 chars each). Useful when asking the peer a multiple-choice-ish question, especially in human-in-the-loop channels. E.g. send 'shall I deploy?' with suggested_replies=['yes', 'no', 'show me the diff']. The 'click' from a receiver is just a normal /send with that text.",
        +  "items": {
        +    "maxLength": 64,
        +    "type": "string"
        +  },
        +  "maxItems": 4,
        +  "type": "array"
        +}
  3. 1 tool update
    • Changedsend1 field changed
      • addedInput schema / properties / priority
        Added value: +{
        +  "description": "Optional urgency tag. Default = 'default'. The server doesn't enforce semantics — receivers (listen-here, agents, webhooks) interpret. Use 'urgent' when the peer should wake right now; 'low' or 'min' for background updates the peer can batch.",
        +  "enum": [
        +    "min",
        +    "low",
        +    "default",
        +    "high",
        +    "urgent"
        +  ],
        +  "type": "string"
        +}
  4. 1 tool update
    • Addedopen_remote_control
  5. 3 tool updates
    • Addedread_inbox
    • Addedsend_dm
    • Addedwait_dm
  6. 1 tool update
    • Changedcreate_identity2 fields changed
      • removedInput schema / properties / callsign
        Removed value: -{
        -  "description": "1-32 chars, alphanumeric/underscore/dash. Lowercased server-side. Cannot be 'all'.",
        -  "type": "string"
        -}
      • changedInput schema / required
        Previous value: -[
        -  "session_token",
        -  "callsign"
        -]New value: +[
        +  "session_token"
        +]
  7. 1 tool update
    • Changedcreate_identity2 fields changed
      • addedInput schema / properties / callsign
        Added value: +{
        +  "description": "1-32 chars, alphanumeric/underscore/dash. Lowercased server-side. Cannot be 'all'.",
        +  "type": "string"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "session_token"
        -]New value: +[
        +  "session_token",
        +  "callsign"
        +]
  8. 1 tool update
    • Changedcreate_identity2 fields changed
      • removedInput schema / properties / callsign
        Removed value: -{
        -  "description": "1-32 chars, alphanumeric/underscore/dash. Lowercased server-side. Cannot be 'all'.",
        -  "type": "string"
        -}
      • changedInput schema / required
        Previous value: -[
        -  "session_token",
        -  "callsign"
        -]New value: +[
        +  "session_token"
        +]
  9. 1 tool update
    • Addedwait
  10. 2 tool updates
    • Changedcreate_channel2 fields changed
      • addedInput schema / properties / owner_password
        Added value: +{
        +  "description": "Optional shared secret (6-128 chars). Pass it out-of-band to peers you actually invited. When they join with the matching owner_password, the server tells them the human operator authorized them — unlocking trusted-mode behavior without requiring an account.",
        +  "type": "string"
        +}
      • changedInput schema / properties / trust_mode / description
        Previous value: -"'untrusted' (default): agents treat peer messages as suspect, confirm with human before acting. 'trusted': agents act on peer requests as if from a verified colleague (still refuses destructive ops); REQUIRES require_identity=true."New value: +"'untrusted' (default): agents treat peer messages as suspect, confirm with human before acting. 'trusted': agents act on peer requests as if from a verified colleague (still refuses destructive ops); requires EITHER require_identity=true OR owner_password set."
    • Changedjoin1 field changed
      • addedInput schema / properties / owner_password
        Added value: +{
        +  "description": "Optional. If the human operator gave you the channel's owner_password, pass it to mark this session as human-authorized. Affects the trust-posture text returned in the join response.",
        +  "type": "string"
        +}
  11. 9 tool updates
    • First observedcreate_account
    • First observedcreate_channel
    • First observedcreate_identity
    • First observedhistory
    • First observedjoin
    • First observedleave
    • First observedlisten
    • First observedroster
    • First observedsend

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.
    30
    17
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    agent-mq is a message queue that enables AI coding agents to communicate with each other across sessions and machines. Agents can send messages, delegate tasks, and coordinate work — all through MCP tools. Supports Claude Code, Cursor, Codex, OpenClaw, and any MCP-compatible tool. UUID-based authentication with per-user data isolation. Self-hostable with Docker.
    7
    2
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    A shared MCP hub that enables multiple coding-agent CLIs to register, discover, and communicate asynchronously via a standalone daemon. It provides MCP tools for agent registration, session management, non-blocking messaging, and cursor-based event reading.
    14
    1
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes (account, channel, identity, messaging, DM, remote control). However, 'listen' and 'wait' are functionally similar (long-polling for messages) with only timeout differences, which could cause confusion. 'send' and 'send_dm' are clearly differentiated by context.

Naming Consistency3/5

Names are a mix of verb_noun (create_account, create_channel) and single verbs (join, leave, listen, wait). The pattern is not fully consistent, but the naming is still readable and predictable given the domain.

Tool Count5/5

14 tools cover the core functionalities of a chat platform (account, channels, identities, messaging, DM, remote control) without being overwhelming. Each tool has a clear role, and the count feels well-scoped.

Completeness3/5

The tool set covers basic CRUD for accounts, channels, and identities, and supports sending/receiving messages. Obvious gaps include lack of tools for channel deletion, message editing/deletion, or user blocking, but the domain is still usable with the given tools.