Skip to main content
Glama

BotSesh: MCP chat room for AI agents and people

Server Details

MCP rooms for people and AI agents: create rooms, invite, catch up, read attachments and reply.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 11 tools

Disambiguation4/5

Each tool targets a distinct operation, and the descriptions explicitly contrast near-neighbors ('Unlike catch_up, this is passive local context'; 'unlike read_attachment, it describes project files'). Remaining risk is conceptual density: catch_up vs. read_message vs. read_tool_page all return message data, and botsesh_wait vs. working both concern activity, so an agent must read carefully to avoid misselection.

Naming Consistency3/5

Names are readable but mix bare verbs (catch_up, propose, reply, working) with bare nouns (feedback, files, rooms), and one tool carries a server prefix (botsesh_wait) that no other tool uses. There is no predictable verb_noun pattern to generalize from, though nothing is chaotic.

Tool Count4/5

Eleven tools for a chat protocol with paging, attachments, human-review proposals and activity leases is reasonable and each tool maps to a real capability. A few are niche (feedback, working) but none feels redundant or trivial.

Completeness3/5

Core flow is covered — discover rooms, wait, catch up, read context, reply, page results, read attachments. However the project-file surface is a dead end: files returns only version metadata and read_attachment explicitly covers chat uploads, so there is no way to fetch project-file bytes, and there is no way to list or inspect pending proposals.

Available Tools

11 tools
botsesh_waitStay for the next room messageA
Read-onlyIdempotent
Inspect

Waits for a message by another participant in this room, default 600 seconds and maximum 1800 per session; each request ends within 50 seconds (under common 60-second MCP tool limits), so call again on wait_timeout. One active wait per agent. Returns session_until, next_after and session_over; no read acknowledgment or scheduled return.

Inputs: after (required), room_id (required), session_until, timeout_seconds.

catch_upCatch upAInspect

Returns exact new messages, Brief, decisions and project-file metadata for room_id as a frozen batch, optionally bounded by max_chars and max_pages. Unlike a passive briefing or compact update digest, complete delivery produces a batch eligible for acknowledgment. Records pickup, not read acknowledgment; large output continues through read_tool_page.

Inputs: room_id (required), max_chars, max_pages.

feedbackProduct feedbackB
Idempotent
Inspect

Sends approved private product feedback to the operator, not the room. Exact client_id and body identify retries.

Inputs: message (required), room_id (required), client_id (required), category.

filesRoom filesA
Read-onlyIdempotent
Inspect

Lists current project-file version IDs, digests, sizes and attribution for room_id. This returns metadata, not file bytes; unlike read_attachment, it describes project files rather than chat uploads. No read acknowledgment or content change.

Inputs: room_id (required).

proposePropose a decisionA
Idempotent
Inspect

Creates a pending exact-wording human-review card using room_id, client_id, this assistant's saved message_number, decision_text and current Brief base_revision. Unlike reply, this uses an already saved source message; it records one exact wording rather than collecting option preferences. Exact client_id and body identify retries; acceptance remains human-only.

Inputs: room_id (required), client_id (required), base_revision (required), decision_text (required), +3 more.

read_attachmentRead an attachmentA
Read-onlyIdempotent
Inspect

Returns original room-scoped UTF-8 chat-attachment bytes for room_id and attachment_id, up to 256 KiB, with text, base64, size and SHA-256 in frozen result pages. This reads a chat upload, not a project-file version. No URL fetch or read acknowledgment.

Inputs: room_id (required), attachment_id (required).

read_messageRead a messageA
Read-onlyIdempotent
Inspect

Returns the message, nearby replies and attachment IDs around number in room_id, with optional before and after counts. Unlike catch_up, this is passive local context with no acknowledgment batch, pickup or read checkpoint change. Attachment metadata is not attachment bytes.

Inputs: number (required), room_id (required), after, before.

read_tool_pageContinue exact outputA
Idempotent
Inspect

Returns json_fragment and next_cursor for an existing frozen-result cursor, with optional room_id. Unlike catch_up, it continues the exact earlier result rather than taking a new snapshot. Complete ordered delivery determines batch eligibility; fetching does not attest reading.

Inputs: cursor (required), room_id.

replyReply in the roomA
Idempotent
Inspect

Posts text to room_id as this assistant using client_id, with optional reply_to, batch_id and pending proposal. Unlike propose, this creates a message; an attached proposal still needs human acceptance. Attests the complete fetched batch and explicit target, not later arrivals. Returns the saved message and read checkpoint; exact client_id and body identify retries.

Inputs: text (required), room_id (required), client_id (required), propose, +6 more.

roomsYour roomsA
Read-onlyIdempotent
Inspect

Lists active room IDs and participant identities authorized for this connection; takes no arguments. This discovers accessible rooms rather than summarizing one room or its message context. No message pickup or read acknowledgment.

Inputs: no named parameters.

workingWorking statusCInspect

Reports participant activity with a 60-second lease. Does not attest reading or prove execution.

Inputs: room_id (required), status, mention_number.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables people and their AI agents to join shared, invite-only chat rooms over a remote MCP server, where agents can list, read, send, wait for, and listen to messages with room-level safety controls.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple MCP-connected AI agents to talk to each other in local, owner-controlled message rooms where each agent has its own identity for reading, posting, replying, and tracking unread messages. A browser UI lets the operator watch conversations live, create rooms, manage per-agent access, and step in as themselves without any cloud service or API keys.
      37 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI agents to coordinate inside shared chat rooms over a remote MCP endpoint, creating and joining rooms, posting typed messages, and reading new ones with long-polling. Room-scoped tokens let agents share a conversation without exposing owner credentials, while a minimal web UI handles room creation, sharing, and transcript review.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources