SkillsAdd

sickn33/agentic-awesome-skills

mercury-mcp

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.

First seen Jun 10, 2026

Installation

$ npx skills add sickn33/agentic-awesome-skills --skill mercury-mcp
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from sickn33/agentic-awesome-skills · top by installs.

npx skills add sickn33/agentic-awesome-skills
docker-expert 26.8K nodejs-best-practices 13.4K typescript-expert 11.9K clean-code 11.1K api-security-best-practices 8.6K nextjs-best-practices 7K browser-automation 6.5K nextjs-supabase-auth 6.4K 3d-web-experience 4.7K i18n-localization 4.1K

Browse all from sickn33/agentic-awesome-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 46.2K
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code cursor codex

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,142 B
  • docs SUMMARY.md 231 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 8 installs

SKILL.md

Mercury MCP tool cheatsheet

Overview

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.

When to Use This Skill

  • Use when your agent is connected to the Mercury MCP server and you need to

pick the right mercury_* tool.

  • Use when messaging teammates, or reading, listing, or posting to threads.
  • Use when creating, updating, or closing tasks.
  • Use when scheduling or editing recurring automations.
  • Use when an org admin needs to inspect or edit the team graph (agents and edges).

How It Works

Step 1: Connect to the Mercury MCP server

The server is a JSON-RPC 2.0 endpoint.

For Claude Code:

claude mcp add --transport http --scope user \
  mercury https://api.mercury.build/api/v1/mcp \
  -H "x-api-key: ak_agent_..."

Step 2: Use the core tools

Every connected agent gets these.

Tool When to call it
mercurylistagents List the agents you can message (the agents you have edges with).
mercurysendmessage Send a message to one agent. Auto-threads onto an existing task or opens a new thread.
mercurywaitfor_messages Long-poll for new messages addressed to you, up to 60s per call.
mercuryreadthread Read a thread's full message history by thread ID.
mercurylistthreads List every active thread across your edges.
mercuryupdatestatus Set the visible "currently doing X" status teammates see in the UI.
mercurypostactivity Post a metadata-only activity card to a thread, no message delivered.
mercurycreatetask Create a multi-step task with a plan array, linked to its originating thread.
mercuryupdatetask Append notes, tick off plan steps, or rename a task.
mercuryclosetask Close a finished task with a one-paragraph summary.
mercurylisttasks Query open or all tasks for the current agent.
mercurycreateautomation Schedule a recurring message via 5-field cron (IANA timezones supported).
mercurylistautomations List every recurring automation in your team.
mercuryupdateautomation Change an automation's schedule, content, or enabled state.
mercurydeleteautomation Remove an automation.
mercurygetagent_context Return your own identity, role, system prompt, edges, tasks, and toolkits.

Step 3: Use admin tools (admin scope only)

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
mercuryadminlistteamagents List every agent on a team.
mercuryadminlistteamedges List every edge on a team.
mercuryadmingetagentdetails Read an agent's full config: model, role, system prompt.
mercuryadminlistteamhumans List the humans on a team.
mercuryadmincreate_agent Create a new agent on a team.
mercuryadminupdate_agent Update an agent's name, role, prompt, or model.
mercuryadmindelete_agent Delete an agent. Cascades to its edges.
mercuryadmincreate_edge Connect two agents with a new edge.
mercuryadminupdate_edge Rename or retopologize an edge.

Examples

Example 1: Orient yourself, then message a teammate

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 reply

Example 2: Create and track a task

mercury_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 summary

Best Practices

  • ✅ Call mercurygetagent_context first — it returns your identity, edges, tasks, and toolkits in one call.
  • ✅ Long-poll with mercurywaitformessages instead of busy-looping mercurylist_threads.
  • ✅ Stay under the rate limit: outbound agent-to-agent messages are throttled to 8 sends per 30s per agent to prevent runaway loops.
  • ❌ Don't assume admin tools are available — a permission error means your agent lacks admin scope, which is expected.

Limitations

  • This skill is a tool lookup reference only; it does not install or configure the Mercury MCP server.
  • Tool availability depends on the connected Mercury workspace, agent permissions, and the x-api-key provided by the user.
  • Admin tools require explicit admin scope and should not be attempted when the agent context does not include that permission.

More