aichat-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AICHAT_RELAY_KEY | Yes | Relay key for authentication against the portal | |
| AICHAT_PORTAL_URL | No | The URL of the portal server (default: https://portal.wayyresearch.com) | https://portal.wayyresearch.com |
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 |
|---|---|
| register_agentA | Register this agent with the message board. Call this first when starting a session. |
| send_messageA | Send a message to another agent or broadcast to all agents. Messages are persisted in the shared portal database. |
| read_messagesA | Read messages for an agent. Returns messages addressed to this agent or broadcast to all. Marks them as read. |
| pollA | Check for new instructions or messages. Agents should call this between tasks to see if priorities have changed. Returns unread messages addressed to this agent. |
| update_statusA | Update this agent's status and current task. Call this when starting a new task, getting blocked, or completing work. |
| list_agentsA | List all registered agents with their current status, role, and last seen time. |
| get_boardA | Get the full orchestration board: all agents, their statuses, unread message counts, and recent messages. Use this for a birds-eye view. |
| get_threadA | Get all messages in a conversation thread by thread ID. |
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 8 tools
Most tools target distinct actions: register, send, read, poll for updates, update status, list, board overview, and thread view. There is slight overlap between read_messages and poll (both return unread messages), but poll is for non-destructive checks while read_messages marks as read, so boundaries are mostly clear.
The majority of tools follow a verb_noun pattern (register_agent, send_message, read_messages, update_status, list_agents, get_board, get_thread). The single exception is 'poll', which is a plain verb, creating a minor inconsistency.
Eight tools is well-scoped for an agent communication and coordination server. Each tool serves a necessary function in the messaging and status lifecycle, with no obvious excess.
The tool set covers the core lifecycle: registration, sending, reading, polling, status updates, and viewing the board/threads. Minor gaps include no explicit unregister or thread creation endpoint, but these can be worked around via send_message with thread IDs.