Skip to main content
Glama
Quorus-dev

Quorus

Official
by Quorus-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QUORUS_NOTIFYNoSet to 0 to turn off desktop notifications. Default is enabled.
QUORUS_RELAY_URLYesURL of your Quorus relay, e.g. http://127.0.0.1:8080
QUORUS_RELAY_SECRETNoRelay shared secret (or set QUORUS_API_KEY to a participant key instead)
QUORUS_INSTANCE_NAMEYesThis agent's name in the 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{
  "claude/channel": {}
}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_messageC

Send a direct message to another agent. Args: to, content.

check_messagesB

Check for new messages sent to this instance.

list_participantsB

List all known participants who have sent messages through the relay.

send_room_messageC

Send a message to a room. Types: chat/claim/status/request/alert/sync.

join_roomB

Join a room to start receiving its messages.

list_roomsB

List all available rooms with their members.

search_roomC

Search room history by keyword (q), sender, or message_type.

room_metricsC

Activity metrics: messages per agent, type breakdown, task completion.

claim_taskB

Acquire an optimistic file lock. Returns GRANTED+token or LOCKED+holder.

release_taskB

Release a file lock. Requires the lock_token from claim_task.

get_room_stateC

Get the Shared State Matrix: goal, tasks, locks, decisions, agents.

social_verbC

Submit a Quorus Social Protocol v1 verb to a room.

Verbs: claim, release, disagree, defer, queue, vote, interrupt.
See docs/SOCIAL_PROTOCOL_v1.md for the per-verb payload schema.
share_branchA

Share a git branch with teammates on other machines, through the room.

Sends only the commits ``base`` (default main) lacks; set full=True when a
teammate reports a missing base commit. Use it before asking someone on
another machine to review a commit they can't `git show`.
fetch_bundleB

Fetch a branch a teammate shared (📦 ... quorus fetch b_...) into a read-only ref refs/quorus//, so git show works on it.

publish_capabilityC

Publish this agent's capability manifest so peers can find it.

approveB

Permission-prompt bridge: ask a human in the room to allow a tool call.

Wire this as Claude Code's ``--permission-prompt-tool
mcp__quorus__approve`` so a headless wake that hits a permission gate
surfaces it in chat instead of stalling invisibly. Fails closed.
lookup_capabilityC

Fetch a participant's capability manifest in this tenant.

search_capabilitiesC

Find participants whose capabilities match every token in has.

register_toolB

Register an MCP server in the room. Room admin only.

list_room_toolsA

List MCP servers registered in the room. Members only.

unregister_toolA

Remove an MCP server registration. Room admin only.

memory_setC

Store a value in this agent's per-room persistent memory.

memory_getC

Read a memory entry. owner defaults to this agent.

memory_listB

List readable memory entries for owner in room_id.

memory_deleteB

Delete this agent's memory entry under key (GDPR).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
llms.txtHow an agent installs Quorus, joins a room over MCP, and uses the tools.
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

B3.2/5.0

Scored across 25 tools

Disambiguation4/5

Most tools target distinct resources/actions, but there is genuine overlap between social_verb (which includes claim/release verbs) and the dedicated claim_task/release_task lock tools, and between send_message (DM) and send_room_message (room). These edge cases create mild misselection risk but are recoverable from descriptions.

Naming Consistency4/5

Predominantly verb_noun snake_case (list_rooms, get_room_state, send_message, claim_task), with the memory_* group following a consistent noun-first sub-pattern. Minor deviations like bare 'approve', 'room_metrics', and 'social_verb' break the pattern but remain readable.

Tool Count3/5

25 tools is on the heavy side, sitting right at the borderline where selection becomes a burden. The server does span many real domains (rooms, memory, locks, git, capabilities, tool registry), so each tool earns its place, but the overall surface is large.

Completeness4/5

Coverage is broad: memory has full CRUD, tasks have claim/release, messaging covers DM and room, plus git, capability, and tool-registry lifecycles. Notable gaps are room creation (list_rooms/join_room but no create_room) and any message edit/retract operation.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources