Skip to main content
Connectors point the other way from the MCP server. The MCP server exposes Monnet to your coding agent; a connector exposes your tools to Monnet, so it can act on them mid-facilitation — searching a ticket while drafting, creating one when the plan calls for it. Connect them from Settings → Integrations in the Workspace section.

​
Available connectors

Atlassian (Jira)

Search, read, create, and comment on Jira issues.

Linear

Search existing issues and create an issue from a motion.

Notion

Search your docs, read pages, and create or edit them. To create motions automatically from a database, set up Notion ambient listening.
Connectors are workspace-scoped: each service has one connection shared by the whole team. Connect it once and Monnet can use it on any motion in that workspace.

​
Connect one

Click Connect on the card and approve on the provider’s consent screen. Monnet acts with the permissions that connection was granted — no more.

​
What Monnet does with them

Nothing on its own. Connecting a tool doesn’t make Monnet crawl Jira, search Linear, or watch Notion databases; it makes that tool reachable when the motion calls for it. In practice that looks like:
  • pulling the current state of a ticket into a motion document instead of asking you to paste it;
  • filing the issues a plan produced, once the plan is agreed;
  • searching Linear for an existing issue before proposing or filing duplicate work;
  • checking a Notion page before asserting something the team already wrote down.
Use playbooks to set connector instructions for a type of motion. Use your workspace Policies for rules that should apply everywhere — for example, always search Linear before proposing work or never create an issue without confirmation.

​
Disconnect

Open the connector card and disconnect. Monnet immediately stops using it; nothing in the external tool is changed or removed.