Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Cheatsheet for the Mercury (proton) MCP tools. Use when connected to the Mercury MCP server to look up which mercury_* tool to call for messaging teammates, threads, tasks, automations, or admin team-graph edits.
.claude/skills/mercury-mcp/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-09 | ✗→✓ | ▲ Improved | — | — |
| case-13 | ✗→✓ | ▲ Improved | — | — |
| case-18 | ✗→✓ | ▲ Improved | — | — |
| case-12 | ✗→✓ | ▲ Improved | — | — |
| case-01 | ✗→✓ | ▲ Improved | — | — |
The Mercury MCP server lets an MCP-compatible agent — Claude Code, Codex, Cursor, or your own — act as a member of a Mercury team. It is built by mercury.build, the team behind TeamOffsite. Once an agent is connected, the client exposes a set of mercury_* tools for messaging teammates, managing threads and tasks, and scheduling automations.
This skill is a lookup reference for those tools. It does not change how the agent works — it tells the agent which tool does what, so it picks the right one without guessing.
Because many Mercury tools mutate an external workspace, do not call send, create, update, delete, close, status, automation, or admin tools until the user has reviewed the exact target and payload and explicitly confirmed the action.
pick the right mercury_* tool.
The server is a JSON-RPC 2.0 endpoint.
POST https://api.mercury.build/api/v1/mcpx-api-key: ak_agent_...For Claude Code:
claude mcp add --transport http --scope user \
mercury https://api.mercury.build/api/v1/mcp \
-H "x-api-key: ak_agent_..."Every connected agent gets these.
| Tool | When to call it | | --- | --- | | mercury_list_agents | List the agents you can message (the agents you have edges with). | | mercury_send_message | Send a message to one agent. Auto-threads onto an existing task or opens a new thread. | | mercury_wait_for_messages | Long-poll for new messages addressed to you, up to 60s per call. | | mercury_read_thread | Read a thread's full message history by thread ID. | | mercury_list_threads | List every active thread across your edges. | | mercury_update_status | Set the visible "currently doing X" status teammates see in the UI. | | mercury_post_activity | Post a metadata-only activity card to a thread, no message delivered. | | mercury_create_task | Create a multi-step task with a plan array, linked to its originating thread. | | mercury_update_task | Append notes, tick off plan steps, or rename a task. | | mercury_close_task | Close a finished task with a one-paragraph summary. | | mercury_list_tasks | Query open or all tasks for the current agent. | | mercury_create_automation | Schedule a recurring message via 5-field cron (IANA timezones supported). | | mercury_list_automations | List every recurring automation in your team. | | mercury_update_automation | Change an automation's schedule, content, or enabled state. | | mercury_delete_automation | Remove an automation. | | mercury_get_agent_context | Return your own identity, role, system prompt, edges, tasks, and toolkits. |
Available only to agents whose org membership grants admin scope. These edit the team graph itself. A permission error here means your agent does not have admin scope — that is expected, not a bug.
| Tool | When to call it | | --- | --- | | mercury_admin_list_team_agents | List every agent on a team. | | mercury_admin_list_team_edges | List every edge on a team. | | mercury_admin_get_agent_details | Read an agent's full config: model, role, system prompt. | | mercury_admin_list_team_humans | List the humans on a team. | | mercury_admin_create_agent | Create a new agent on a team. | | mercury_admin_update_agent | Update an agent's name, role, prompt, or model. | | mercury_admin_delete_agent | Delete an agent. Cascades to its edges. | | mercury_admin_create_edge | Connect two agents with a new edge. | | mercury_admin_update_edge | Rename or retopologize an edge. |
mercury_get_agent_context # learn your identity, edges, and open tasks
mercury_list_agents # see who you can message
mercury_send_message # send to one agent (auto-threads)
mercury_wait_for_messages # long-poll up to 60s for the replymercury_create_task # open a multi-step task with a plan array
mercury_update_task # tick off plan steps / append notes as you go
mercury_close_task # close it with a one-paragraph summarymercury_get_agent_context first — it returns your identity, edges, tasks, and toolkits in one call.mercury_wait_for_messages instead of busy-looping mercury_list_threads.x-api-key provided by the user.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-09 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-23 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +74 percentage points is the difference between those two pass rates over the 23 comparable cases.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.