Your Merryman,
in your assistant.

Add to Claude

1. Claude opens with Merrymen already filled in. Click Continue, then Connect.
2. Merrymen opens. Sign in if asked, then click Allow.
3. Back in Claude, ask “Why hasn’t my agent traded?”

Add it once and it works on claude.ai and in the Claude desktop and mobile apps. Claude Code signed in to the same account gets it too.

On a Team or Enterprise plan? Your organisation’s owner adds it once: add Merrymen for your organisation (opens in a new tab). Everyone else then finds Merrymen in Claude under Customize → Connectors and clicks Connect. Claude’s free plan allows one custom connector.

Other assistants

• Claude Code

  In Claude Code, run these one at a time:

  /plugin marketplace add https://github.com/millw14/merrymen.git

  Copy

  /plugin install merrymen@merrymen

  Copy

  Then type /mcp, choose Merrymen and Authenticate. You get /merrymen:status, /merrymen:why, /merrymen:portfolio and more, or just ask.

  Added Merrymen to Claude already? Claude Code signed in to the same account has it too. Without the plugin, from a terminal:

  claude mcp add --transport http --scope user merrymen https://mcp.merrymen.dev/mcp
  claude mcp login merrymen

  Copy

  Or just tell Claude Code:

  Set up the Merrymen MCP server. Instructions: https://merrymen.dev/llms.txt

  Copy

• ChatGPT

  Turn on Developer mode (Settings → Security and login), then create an app with the address below.

  Copy addressOpen ChatGPT (opens in a new tab)

• Grok

  One-time setup in Grok: open Plugins → Connectors → New Connector → Custom. Set Name to Merrymen, paste this address into Server URL, then choose Add Connector.

  Copy addressOpen Grok connectors (opens in a new tab)

  Asking Grok chat to “connect Merrymen” by name does not install this unlisted custom connector. Add it manually once, then complete the Merrymen sign-in and choose what to allow.

  After connecting, ask “Help me set up my Merryman and check whether it is running.” If you need a new Merryman, allow setup drafts when connecting. Review its setup and approve its wallet permissions in Merrymen, then return to Grok to check its actual status.

  No model API key needed. Business and Enterprise accounts may need an administrator to provision the connector. Grok’s connector guide (opens in a new tab)

• Grok Bot

  Give your Bot this setup prompt. It guides the connection, your Merryman’s setup and the final status check:

  Copy setup prompt
  Read the setup prompt

  Help me connect Merrymen to this Grok Bot and set up or check my hosted Merryman.
  
  Read the setup instructions at https://merrymen.dev/llms.txt. Use only this remote MCP server: https://mcp.merrymen.dev/mcp.
  
  Check this Bot's installed MCP connections first. Reuse a working connection at that exact address; do not assume a Grok chat connector is installed in this Bot. If unavailable, guide me through adding the remote server using the supported connection settings. Do not claim it is connected until a tool call succeeds.
  
  Use OAuth. Send sign-in and consent links to me to open in the browser on my own device. Do not sign in to Merrymen, approve proposals, create wallets or sign permissions through the Bot's shared cloud computer. Never request keys, recovery phrases, passwords or bearer tokens in chat.
  
  For a requested setup, call get_merryman_setup before acting and use only the available tools and their schemas. Reuse the selected agent and saved wallet; an empty list is not evidence that no wallet exists. A status question does not authorize a new draft.
  Use preferences already supplied without asking again. Before creating, inspect a known proposal with get_proposal, or list_proposals with status=all when available, and resume the matching setup, including an approved draft awaiting signing. Ask only when the intended agent/proposal is ambiguous or supplied choices conflict. Do not replace an existing agent or alter its settings just to complete setup.
  For a requested new setup with no strategy, asset or basket preference and no live-mode request, disclose this practice starter before preparing the draft: {"name":"My Merryman","strategy":"steady-basket","asset_mode":"stocks","risk_level":"careful"}. Preserve any supplied name/risk choice. Leave the basket to Merrymen's owner-review defaults unless the owner supplied one. Otherwise preserve the owner's configuration and omit unspecified optional fields; ask only for a missing choice required to make it valid. These defaults never change an existing agent. Mode is an owner choice, not a create_merryman argument: do not send mode, wallet, signing or limit fields.
  Use create_merryman only if that tool is granted. Choose one idempotency_key per distinct draft and retain it with the proposal ID. After an uncertain result, inspect that proposal or recent proposals; do not create another draft with a fresh key. If drafting is unavailable, offer the returned owner creation link and explain optional drafting access without automatically expanding scopes.
  Return one approval_url with a short summary of the prepared choices and intended mode. The owner reviews and continues through account/wallet setup, mode selection and signing on their own device; never perform signup, consent or signing on a shared cloud computer. After the owner returns, call get_merryman_setup again and get_agent_status if available. Report practice active only when setup reports phase=paper with a fresh worker report; otherwise state the actual phase and blocker. Signing or approval alone is not activation.
  
  Use text and links if this host cannot render MCP Apps. Merrymen's hosted worker runs the agent; this Bot and chat do not need to stay open. Do not start a second worker or set up a trading loop here.
  
  For later requests, use only tools this connection grants. Keep practice and live results separate. Never weaken signed limits or retry a financial action whose outcome is unknown. A proposal or submitted order is not a confirmed trade.
  
  Do not create a monitoring routine unless I ask. If I do, use read-only status, portfolio and decision tools; notify me only of meaningful changes or required action. Do not create drafts, propose or approve trades, change settings or retry orders in a routine.

  Open sign-in, setup and approval links on your own device. Keep wallet signing in your own browser; Grok Bot’s cloud computer is shared with its bots.

  Manual connection options

  Grok Bot supports Cursor-compatible MCP servers. If its settings ask for MCP configuration, use:

  {
    "mcpServers": {
      "merrymen": {
        "url": "https://mcp.merrymen.dev/mcp"
      }
    }
  }

  Copy

  Using Grok CLI on your own computer? Add Merrymen with:

  grok mcp add --transport http merrymen https://mcp.merrymen.dev/mcp

  Copy

  Grok CLI opens OAuth in your browser when the server needs it. Use /mcps to manage servers; select Merrymen and press i to authenticate if needed.

  Connect inside the Bot separately; don’t assume a grok.com connection carries over. If cards are unavailable, ask for the status in text and open approval links yourself. Grok Bot guide (opens in a new tab)

• Codex

  codex mcp add merrymen --url https://mcp.merrymen.dev/mcp

  Copy

  It opens Merrymen to sign in by itself. The Codex app and IDE extension pick it up too.

• Cursor

  Add to Cursor (opens in a new tab)

• VS Code

  Add to VS Code (opens in a new tab)Insiders