Integrations

Overview

Moonage reaches your tools through MCP servers, called live at the moment an agent needs them. When an agent asks what is blocking a launch, it calls Linear right then and reads what Linear returns.

There is no bulk import, no index to build, and no sync schedule to wait on. Nothing is copied into Moonage ahead of time, so there is nothing to go stale between runs.

How a connection works

1. Connect — authorize the tool over OAuth from the desktop app.
2. Grant — lend the connection to a Space, so the work happening there can use it.
3. Use — agents call the tool live, in the middle of the work.
4. Gate — consequential actions stop for a human decision and surface in the Inbox.

Connecting tools is part of setting up a Space: you add the people and agents, then connect the tools that work needs. Onboarding an agent also shows you the integrations that agent will reach, before it does anything.

Available connectors

• Atlassian (Jira + Confluence)
• Cloudflare
• Fireflies
• GitHub
• Google Workspace
• Granola
• HubSpot
• Linear
• Mercury
• Microsoft OneDrive
• Microsoft Outlook
• Notion
• Slack
• Trello

Some connectors cover a whole suite. Google Workspace is one connection, not separate Gmail, Calendar, and Drive connections. Atlassian is one connection covering both Jira and Confluence.

What an agent can do with a connection

A connected tool becomes something the agent can both read and act on. In practice you ask for the work, not for the integration:

"What's blocking the launch in Linear?"
"Summarize the #engineering thread about last night's deploy"
"Open a GitHub issue for the regression we just found"
"Post the summary back to the channel when it's ready"

Reads happen immediately. Writes and other consequential actions stop at a human gate and land in the Inbox for approval before anything leaves Moonage. How much stops for approval depends on the agent's autonomy level — Observe, Advise, Execute, or Autonomous — resolved per action from the risk, the scope, and the responsible human.

Who holds a connection

Connections are held per member, not per Space. You authorize Slack once, under your own account, and that connection is yours. You then grant it to the Spaces where it should be usable, and agents working in those Spaces act through the grant.

This means two people in the same Space can each hold their own connection to the same tool, and each connection carries only the access its own authorization was given. Revoke the grant and the Space loses the connection; the connection itself stays with the member who made it.

Authentication

Every connector authorizes over OAuth; Trello uses OAuth 1. There are no API keys anywhere in Moonage — nothing to paste, nothing to rotate by hand.

OAuth access tokens, refresh tokens, and provider client secrets are encrypted with AES-256-GCM before storage, under rotatable keys.

Every action taken through a connection is attributable and replayable in the audit log.

Beyond the built-in connectors

The 14 connectors above are the ones Moonage ships with a first-class setup flow. They are not the limit.

Any compatible MCP server can be connected, including servers your own team runs. Once connected, it behaves like any other integration: called live, granted to Spaces, and subject to the same gates and audit trail.

Not to be confused with the Moonage MCP

This page is about connecting external MCP servers into Moonage, so your agents can use your tools.

The Moonage MCP points the other way: it exposes your Moonage workspace to an outside MCP client, such as a coding assistant. That is covered in the API reference.

If you have not set up an organization yet, start with Getting Started.