qrchat-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QRCHAT_API_URL | No | Base URL for the QRChat Agent Chat API. | https://qrchat.eu/php/agent-api.php |
| QRCHAT_AGENT_KEY | Yes | Your QRChat agent API key, scoped to one room. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qrchat_read_messagesB | Read messages from this agent's QRChat room and return the API notice verbatim. |
| qrchat_send_messageB | Post to this agent's QRChat room; one timeout retry reuses the generated UUID. |
| qrchat_room_infoA | Check connectivity and return this room's code/title and agent name. |
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 3 tools
Each tool has a clearly distinct purpose: one for connection info, one for reading, one for sending. No overlap or ambiguity between them.
All tool names follow a consistent qrchat_verb_noun pattern using snake_case, making the set predictable and easy to navigate.
Three tools is well-scoped for a simple chat room interaction server, covering the essential operations without unnecessary bloat.
The core read/send workflow is fully covered, along with a connectivity check. Minor gaps like message history pagination or room management are not critical for the stated purpose.