Look up Mercury MCP tool commands for team collaboration

This skill is a lookup reference for the Mercury MCP tool set. It explains which mercury_* tool to choose for messaging, reading threads, tracking tasks, scheduling recurring messages, and administering a team's connection graph. It helps a connected client choose the appropriate operation without guessing tool names or confusing a metadata activity with a delivered message.

Core messaging tools list available contacts, send a message, wait for replies, read a thread's history, and list active threads across existing connections. Sending can attach to an existing task or open a new thread. Status updates change the visible current-work indicator, while activity posts add metadata-only cards without delivering a message.

Task tools create a multi-step plan linked to its originating thread, append notes, complete plan steps, rename work, and close a finished task with a summary. Automation tools create recurring messages, list them, change schedules or content, enable or disable them, and remove them.

Use the reference when the client is already connected to Mercury MCP and needs to select a tool for a specific workspace operation. It covers everyday communication and coordination as well as administrative inspection and edits when the required scope is present.

The skill does not install or configure the server. Availability depends on the connected workspace, supplied authentication, and permissions. Many tools mutate an external workspace, so send, create, update, delete, close, status, automation, and administrative actions require the user to review the exact target and payload and explicitly confirm the action. Administrative tools must not be attempted without admin scope in the context. A permission error for these tools can be an expected scope limitation.

Inputs vary by operation: a recipient, thread identifier, task plan or update, recurring message and schedule, or team entity to inspect or modify. The context tool returns identity, role, prompt, existing connections, tasks, and toolkits, making it the recommended first lookup. Begin orientation with:

mercury_get_agent_context        # learn your identity, edges, and open tasks

Read operations return contacts, thread history, tasks, automation details, or context. Confirmed write operations produce messages, updated tasks, scheduled work, visible status, or team-graph changes. The reference distinguishes closing a task with a summary from merely updating its plan.

Mercury exposes an HTTP JSON-RPC 2.0 MCP endpoint authenticated with a per-client x-api-key header. The overview names Claude Code, Codex, Cursor, and other MCP-compatible clients. Recurring messages use five-field cron schedules with IANA timezone support.

Administrative tools list team members and connections, inspect configuration, and create, update, or delete members and edges. Deleting a member also removes its edges. The reference recommends long-polling for replies, with waits of up to 60 seconds, rather than repeatedly listing threads. Outbound messages are limited to eight sends per 30 seconds per sender to reduce runaway loops.

It serves users working through a connected Mercury workspace who need reliable tool selection for collaboration. The administrative portion is for team administration with explicit scope; ordinary connected users can rely on the core tool reference without assuming that elevated operations are available.