Monroe

Connect your tools

Model Context Protocol (MCP)

Use Brain from Claude or ChatGPT

In Dashboard → Channels → Agents, copy https://mcp.getmonroe.com/mcp into a remote custom agent connector. Sign in with Monroe, choose the firm workspace, and approve the requested Clerk access.

Connections start with Brain, Decks, and Workspace tools read-only and Agent access disabled. Read-only tools can search and fetch the firm's live Brain, inspect history and relationships, list recently generated presentation decks, workspace activity, members, scheduled workflows, and billing-period usage, and return links to canonical Monroe records. A workspace owner or admin can separately enable Agent access so the outside client can ask Monroe to answer or perform bounded work through its normal agent loop.

Access is controlled per tool group in Agents. Brain, Decks, Workspace, and Agent can each be set to Disabled or Read only for every connection — and Brain additionally to Reviewed writes. Agent access returns a final answer from Monroe; it does not stream progress, approve gated actions, or expose generated files through the external connector. A disabled group rejects its tools on the next call.

Reviewed writes never let the outside agent save arbitrary data. The agent creates an exact proposal, a member reviews individual facts and relationships in Monroe, and the agent can commit only that immutable approved subset. Monroe exposes no external delete tool.

Revoke a client from Agents to block its next Monroe request. Removing the member or suspending the workspace also blocks access immediately.

Shipping in stages. Monroe's runtime is an MCP client today, and the dashboard's unified Tools & data surface is where customers connect managed app integrations. The app catalog covers long-tail tools such as Linear, Snowflake, Airtable, Asana, Jira, Confluence, Intercom, and Zendesk. Custom/private MCP servers are currently wired with the Monroe team so credentials, network exposure, and approval rules are reviewed before the agent can use them.

MCP is an open standard for letting AI agents call tools. Monroe is a first-class MCP client: any approved MCP server you point Monroe at becomes part of its toolkit.

Why this matters

Managed app connectors cover the major-vendor long tail. But what about:

  • Your internal deal-pipeline dashboards
  • Your custom-built CRM
  • That niche industry SaaS your team uses but no AI tool supports
  • A new tool that launched yesterday

If it exposes a stable MCP server or API, Monroe can usually reach it.

Adding an MCP server

Start in Dashboard → Tools & data and search the app catalog first. If the tool is not there, or if you want to connect a private MCP server, email enterprise@getmonroe.com with the server URL, auth method, and the workspace that should receive it:

https://your-internal-tool.example.com/mcp
Bearer your-internal-tool-token

Monroe validates the connection, reviews the auth boundary, reads the server's tool schema, and adds approved tools to the workspace agent. From the next conversation forward, Monroe can call them.

Building an MCP server

If the tool you want doesn't have an MCP server, we recommend:

  1. Official servers: github.com/modelcontextprotocol/servers: 100+ pre-built including Postgres, Filesystem, Brave Search, etc.
  2. FastMCP: Python framework for spinning one up in ~50 lines. See the FastMCP docs for an example template.
  3. TypeScript MCP SDK: official SDK for Node/Bun servers.

Security

MCP servers run in your environment, not ours. We connect to them; we never proxy them through Monroe's infrastructure. If your server is behind a VPN, expose it through your firm's approved tunnel, gateway, or allowlisted endpoint.

For sensitive servers, set up:

  • Token-based auth or another revocable service credential
  • Network restrictions that allow Monroe's agreed egress path only
  • Audit logging on the server side

The catalog

The app catalog in Dashboard → Tools & data is the self-serve path for managed business tools. It includes document systems, CRM/revenue tools, project trackers, data warehouses, support systems, and CRE-specific systems where the vendor exposes a stable connection. Use custom MCP only when the tool is private, internal, or not available in the app catalog.

Next → audit log.