A
licenseA
qualityD
maintenanceBridges any MCP client (like Claude Code, Zed, VS Code) to any ACP coding agent, enabling multi-agent orchestration from a single chat interface.
24
119
9
Apache 2.0
RogerRat
Server Details
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- opcastil11/rogerthat
- GitHub Stars
- 1
- Server Listing
- RogerThat
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 4.4/5 across 14 of 14 tools scored. Lowest: 3.4/5.
Server CoherenceA
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceA 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.2113MIT
- AlicenseBqualityDmaintenanceagent-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.72MIT
- Alicense-qualityBmaintenanceA 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.21MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.