Skip to content
Docs · Claude Code plugin

MCP server

The Claude Code plugin

One install connects Claude Code to Yomenie and shows every sub-agent it starts on the floor beside you. Two commands, a browser sign-in, no tokens.

Updated

On this page

The Yomenie plugin for Claude Code does three things:

  • Connects Claude Code to Yomenie with the same MCP server as claude mcp add, so it can work with your tickets and chat as you.
  • Shows its sub-agents on the floor. Every sub-agent Claude Code starts appears as a small violet helper at your desk while it works, and leaves when it’s done. The plugin makes sure of it, so you don’t have to ask.
  • Knows its way around. A short skill (yo:yomenie) tells Claude when to reach for tickets, chat and helpers.

Install

In Claude Code, type these one after the other:

/plugin marketplace add https://yomenie.us/claude-code/marketplace.json
/plugin install yo@yomenie

Or in your terminal:

claude plugin marketplace add https://yomenie.us/claude-code/marketplace.json
claude plugin install yo@yomenie

The plugin is called yo, so claude plugin install yo works too once the marketplace is added. Then run /mcp, pick plugin:yo:yomenie and choose Authenticate. Your browser opens for the sign-in and consent, the same as for claude mcp add. The same steps are in Yomenie under Settings → Connected apps and in the “Connect Claude Code or Codex” popover on the Board and in Chat, each with a Copy button.

Already connected with claude mcp add? Remove that server (claude mcp remove yomenie) so Claude Code doesn’t have two Yomenie connections, then revoke the old one in Settings → Connected apps.

How sub-agents reach the floor

Claude Code’s hooks can’t call Yomenie themselves, and the plugin never sees your sign-in. Instead, the hooks tell Claude what to do, and Claude makes the calls over its own connection:

  1. When a session starts, Claude is told the routine: before it starts a sub-agent, register it with start_helper (a role, a short task and the ticket if there is one), and end it with end_helper when it returns. When it works on a ticket it doesn’t claim (the branch names it), it puts that ticket on its session with update_helper, so the floor shows it.
  2. When Claude starts a sub-agent without registering it, the plugin holds that one start back with the exact start_helper call to make. Claude makes it and starts the sub-agent again, with its helper id in the prompt. If Yomenie isn’t available, Claude notes that and carries on.
  3. Inside the sub-agent, it’s told to pass its helper id on the Yomenie tools it calls, so its comments and messages read “via Claude Code (Pip)”.
  4. When the sub-agent returns, Claude is reminded to call end_helper with its id.
  5. When Claude asks you something and waits, it marks the helper waiting (update_helper with waiting), so you get “Pip is waiting for you” under the bell and on your devices; it clears on Claude’s next call.

This costs one call before and one after each sub-agent. Sub-agents that start their own sub-agents only get a reminder.

To keep the reminders but never hold anything back, set YOMENIE_HELPERS=remind in your environment; YOMENIE_HELPERS=off silences the hooks. To hide your helpers from your team, turn off Show my agents on the floor in Settings → Profile.

The hooks need node on your PATH. Without it, the plugin still connects and the skill still works; only the hooks stay quiet.

Updates and removal

To get the newest version: claude plugin marketplace update yomenie, then claude plugin update yo@yomenie. To turn it off for a while: claude plugin disable yo (and claude plugin enable yo to bring it back). To remove it: claude plugin uninstall yo@yomenie, then revoke its connection in Settings → Connected apps.

Other tools

Codex, Cursor, VS Code and OpenClaw connect to the same server without a plugin: see Connect your tool. Their sub-agents can still register as helpers through the helper tools; the server’s own instructions ask them to.