Read, post, comment, reply, react, and join groups on Facebook as the logged-in user, through a real browser. Use whenever the user asks to do something on Facebook.

Everything goes through **`gw`**, already authenticated for this account. Run `gw` for the groups, `gw <group>` for a group's commands and their flags: that help is generated from the tool itself, so it is never stale.

Pick by what you already know:

Hand a task to another of the owner's sandboxes that is linked to this one (`mcp__<sandbox>__delegate`, or `agents delegate` from a shell), and supervise it like a subagent. Use when the work needs what only that sandbox has (its credentials, its repos, its devices, its persona), not for more hands on this sandbox's own work, which is `spawn`.

Everything goes through **`m365`**. This connection is `${id}`; when several Microsoft 365 cards are connected, every command takes `--account ${id}` (`m365 accounts` lists them). `m365 --help` lists every command and flag. Output is JSON; a failure prints `m365: …` with exit code 2 and says what

Home: https://www.npmjs.com · a package: https://www.npmjs.com/package/<NAME> · account menu (tokens, 2FA, packages) is under the avatar, top right.

Read and manage Redmine projects, issues, and updates via the Redmine REST API. Use when the user asks about Redmine tickets/issues or projects.

Read and write SharePoint sites, document libraries, files and lists through Microsoft Graph. Use when the user asks about SharePoint sites, team documents, shared files, or SharePoint lists.

This sandbox can act on the account that owns it: list its sandboxes, create new ones on the owner's own computers, and take one away. You reach that with the `sandboxes` command. The provisioning token behind it lives with the daemon and is never in your environment, so nothing you can read or run

This sandbox can hold a USDC balance and spend it on the open web: any endpoint that charges per request over the x402 protocol (HTTP 402 + a machine-readable price). You reach it with the `wallet` command. The wallet's signing key lives with the platform, never in this container: you can ask for a

Run turbo against the connected Turborepo remote cache, so a typecheck, build or test replays what CI already computed and hands CI what this sandbox checked. Use when running turbo tasks in a repository whose CI shares this cache, or when the user asks about the shared turbo cache.

One page: