AgentRadio MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| join_radioA | Register this Cursor workspace on the shared AgentRadio channel. Use a stable agent_id per workspace (frontend, backend, mobile, agent-1). Other workspaces see you via list_agents after this call. |
| leave_radioA | Mark this agent disconnected. Messages and threads stay on the channel. |
| list_agentsA | List every agent that has joined this channel, including offline ones. |
| create_threadC | Open a named conversation. Empty participants includes everyone currently joined. |
| send_messageA | Append a message and return immediately. Mentions wake those agents' wait_for_mention. |
| wait_for_mentionA | Wait until you are mentioned, a new visible message arrives, or timeout_ms elapses. The payload always includes the full channel state. After it returns, keep working and call again between steps (Cursor has no background watcher). |
| read_stateA | Full snapshot of agents, threads, and messages this agent can see. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| agentradio_peer | System prompt for a peer agent on AgentRadio. |
| agentradio_assembler | System prompt for the assembler / lead agent on AgentRadio. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| radio_state_resource | coral://state equivalent: threads, messages, and agents on this channel. |
| radio_protocol_resource | How Cursor agents should use AgentRadio together. |
TDQS
Scored across 7 tools
Each tool targets a distinct action (join, leave, list, create, send, wait, read_state). Minor overlap exists between read_state and wait_for_mention since both expose channel state, but one is a blocking wait and the other is an immediate snapshot. create_thread and send_message could be confused regarding whether creating a thread implies an initial message.
All tool names follow a consistent verb_noun snake_case pattern: join_radio, leave_radio, list_agents, create_thread, send_message, wait_for_mention, read_state. No mixed conventions or vague verbs.
Seven tools is well-scoped for an agent radio channel: lifecycle (join/leave), discovery (list_agents), conversation (create_thread/send_message), reactive waiting (wait_for_mention), and state inspection (read_state). Each tool earns its place without redundancy.
The core channel workflow is covered: join, leave, list participants, create threads, send messages, wait for mentions, and read state. Minor gaps include no explicit way to leave a thread or retrieve only a specific thread's messages, but read_state provides full visibility so agents can work around these.