Monroe
Sign inGet started

Documentation

Hire Monroe. Then put it to work.

Monroe lives in Slack and Microsoft Teams. After a 5-minute setup, you connect the tools you already use, set a budget, and Monroe starts handling the ops work your team would otherwise do manually. These docs are organized for two audiences: operators who want to get the most out of Monroe in their workspace, and builders who want to extend Monroe with custom skills, MCP servers, and webhooks.

Get started fast

If you have 5 minutes, start here:

  • Hire Monroe in 5 minutes — Sign up, install in Slack or Teams, run your first task. Most teams have Monroe shipping real work by the end.
  • Your first task — Three example workflows new teams run on day one. Copy them, adapt, tell Monroe to handle them on a schedule.

Read the manual

The full conceptual model in four short pages:

  • Workspaces — one Monroe per workspace, isolated, persistent. How shared state works across your team.
  • Credits and billing — what a credit is, how to read your usage, when overage starts, how to raise or lower your cap.
  • Approval gates — how Monroe decides what needs your OK before executing, and how to customize the approval rules for your team.
  • Skills — procedural learning. Monroe gets better at your team’s specific workflows over time. How to teach it, how to inspect what it knows, how to roll back.

Connect your stack

Slack and Teams are the surfaces. Everything else is OAuth, MCP, or webhook:

  • Slack install — one-click install, then choose channels, then set approval rules.
  • Microsoft Teams install — tenant authorization, manifest install, and channel mapping.
  • OAuth connectors — Drive, GitHub, HubSpot, Stripe, Notion, Linear, and the rest. Per-connector scoping and revocation.
  • Model Context Protocol (MCP) — add any MCP server to extend Monroe’s capabilities to the long tail of internal and niche tools.

Trust & compliance

  • Security overview — per-workspace isolation, OAuth-only credentials, hard spend caps, approval gates, run receipts, SOC 2 status.
  • Audit log — every run, every tool call, every approval decision. Export to S3, Splunk, or syslog on Enterprise.
  • Data residency — US-East default. EU-West and AP-Southeast available on Enterprise.

Build with Monroe

  • Webhook API — trigger Monroe runs from any system that can POST JSON.
  • Run receipt format — the wire format for the post-run summaries Monroe posts in-channel.
  • Changelog — every shipped change, dated.

Stuck? Email support@getmonroe.com — we reply within a business day on Solo, faster on Team / Business / Enterprise.