Using Minion

Minion is the personal assistant platform for builders who would rather own their automations than rent them.

Minion gives your AI assistant secure, reusable access to your services and lets it run durable Worker-native automations while your computer is offline.

These docs are for people who connect their assistant to Minion over MCP (see the docs index ). The in-app Get started page (/app/onboarding) connects an app, has you say hello from it, then proves the same home works from a second app. People with a Minion account can also join the community .

Read in order for a full tour, or jump to a topic.

Docs

The user-facing docs site is minion.codes/docs : an introduction, Get started, Concepts, Examples, Packages, Integrations, and per-provider connection walkthroughs. Every page is also raw markdown (/docs/<slug>.md), indexed at minion.codes/llms.txt . Connected agents open built-in guides with search({ entities: ["guide:{id}"] }). The pages below are the MCP-level reference detail those docs link into.

• What is Minion? — the introduction: what Minion is and is not, what you cannot get elsewhere, the building blocks
• Search and execute — the two MCP tools: find the right thing, then run it
• Connect your agent — the three-step Get started flow for people
• Shared memory , Secrets , and Jobs, workflows, and webhooks — concept docs for the primitives every connected agent shares
• Flake Hunter , Sentry Issues , Agent inbox , and Purchase thanks — worked examples of triggers (cron, webhook, email, event)
• Connect a provider — verified walkthroughs for connecting Discord, GitHub, Google, and other providers to Minion
• How Minion works — ask once, save an export, daily email only when something shipped
• The Minion factory map — the primitives your assistant gets and the boundary around local files and processes
• Packages, integrations, and MCP servers — when those three look interchangeable
• OAuth integrations — request narrow provider scopes; integrations are organization-level credentials, not package-specific grants.
• Lock an MCP server to a package — keep minion.mcp["name"] off execute and other packages
• Connect a home MCP server — run a local MCP process (vault, CLI, or home devices), publish it with Tunnel and Access, and connect it to Minion. Starter: home-mcp-starter
• Connect your agent (host notes) — per-host install steps and the setup prompt
• Connect remote MCP servers — add external MCP servers so Minion can call their tools (minion.mcp[...])
• First steps — what to ask Minion to do
• Tasks — a shared team todo list with tags, priorities, due dates, completion, and agent/API access
• Search
• Execute and workflows — includes per-user MCP instruction overlays and package imports
• Workflows
• Packages
• Sharing packages : reuse packages inside your team. Sharing with other teams isn't available yet
• Runtime and limits — what a run is, what each surface counts against, per-run limits, and the monthly worker compute include
• Offload work that does not fit a Worker isolate — large npm graphs (PDF.js-class libraries) stay out of the package isolate; the owner operates a container or machine and the package calls it
• Editing package source — open a repo session, edit files, and publish a new version
• Raw MCP content blocks
• Secrets and host approval
• Email primitives — the team inbox, verified destinations, and replies
• Inbound webhooks — team-owned HTTPS endpoints that dispatch provider POSTs to a saved-package export
• Package apps — serve a Hono app from a package at https://<org>.runminion.run/<package>/
• Synthetic event dispatch — interactive MCP post-publish smoke test for one subscription handler
• Waiting — current-state items only a person can clear (/app/waiting and minion.waiting.list)
• Activity — failures and recent runs for jobs, apps, webhooks, and other runtimes (/app/activity and the runs MCP capabilities)
• Plans and pricing — free and paid plans, plus prepaid credits for worker compute past a plan's monthly include
• Mutating actions and confirmations
• Privacy — what Minion stores, how connected accounts work, and what you can export or delete (Terms of Service are at minion.codes/terms-of-service )
• Troubleshooting — common MCP issues
• Memory and conversation context
• Community Project mark — logo for unofficial integrations and community-built tools

Contributing to these docs

Authors and maintainers follow the conventions of the existing docs . Usage pages stay short; the MCP server favors concise tool descriptions and puts detail where it belongs after each tool runs.